@agimon-ai/po-browse-tool@0.0.0-alpha.18
MCP server for browser automation using Playwright with profile management, page registry, and multi-browser support
AI Security Review
scanned 16d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete exfiltration behavior. The flagged execution and process-output handling support the package’s caller-invoked browser automation and diagnostics.
Decision evidence
public snapshot- The manifest exposes library and CLI entrypoints; its scripts are development and build tasks, with no install hook.
- The runtime API binds browser actions to a profile and blocks navigation URLs containing secrets.
- Custom code runs through the browser automation interface using the supplied page, context, or browser; snippets are loaded from a configured directory.
- Captured browser process output is used in extension startup failure diagnostics.
- Chrome for Testing metadata comes from its published feed, and the package downloads the selected browser archive.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/dockerChromeForTesting-BMmEQq88.mjsView on unpkg · L1A single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/dockerChromeForTesting-BMmEQq88.mjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @agimon-ai/po-browse-tool@0.0.0-alpha.18.
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.18 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.