@agimon-ai/po-browse-tool@0.0.0-alpha.89
MCP server for browser automation using Playwright with profile management, page registry, and multi-browser support
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package’s browser execution and Chrome download behavior fit its stated purpose, and it has no install hook. However, runtime logging is enabled by default without a located disclosure, while the inspected source does not reveal enough about the telemetry payload or endpoint to establish a more severe finding.
Decision evidence
public snapshot- The package exports its main CommonJS and ESM entry points from dist/index.cjs and dist/index.mjs.
- The manifest declares build, test, typecheck and lint scripts but no install lifecycle scripts.
- The runtime telemetry manager enables logs unless OTEL_SDK_DISABLED is set; the package README search found no telemetry disclosure.
- Chrome for Testing metadata is fetched from the official googlechromelabs.github.io release feed as part of browser setup.
- The package is described as an MCP server for Playwright browser automation, which accounts for browser process execution and browser-related network activity.
- The stdio server starts through an explicit start() call, and the manifest has no install hooks.
- The inspected source does not establish that telemetry sends credentials, file contents, prompts, code or tool output.
Source & flagged code
8 flaggedFindings
Affected versions and remediation
This report applies to @agimon-ai/po-browse-tool@0.0.0-alpha.89.
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.89 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.