@agimon-ai/po-browse-tool@0.0.0-alpha.50
MCP server for browser automation using Playwright with profile management, page registry, and multi-browser support
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe package’s intended browser automation tool executes caller-supplied JavaScript in the host runtime, creating a real code execution risk. The inspected source shows no automatic install trigger or independent malicious transfer, so this warrants a warning rather than a block.
Decision evidence
public snapshot- The package manifest lists build and development scripts, with no install lifecycle hook shown.
- The runtime registers a browser_run_code tool that accepts JavaScript snippets.
- The tool compiles supplied code with the Function constructor in the package runtime, with page, context, and browser as parameters.
- The tool passes caller-supplied code to that compiler and returns its result in the tool response.
- The ESM entrypoint contains the same Function-based execution behavior.
- Code execution requires a caller to invoke the browser tool; the source does not show this behavior running during installation.
- The reviewed path returns results through the tool response and does not identify a fixed external recipient.
Source & flagged code
8 flaggedFindings
Affected versions and remediation
This report applies to @agimon-ai/po-browse-tool@0.0.0-alpha.50.
See all versions of @agimon-ai/po-browse-tool for other recorded verdicts.
- Review the evidence and your use of @agimon-ai/po-browse-tool@0.0.0-alpha.50 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.