@agimon-ai/po-browse-tool@0.0.0-alpha.14
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-aiThe manifest has no install lifecycle hook, and inspected runtime behavior is consistent with browser automation and browser setup. Scanner signals for process output and networking resolve to local process capture, configured tool forwarding, and Chrome metadata retrieval; no concrete attack behavior was established.
Decision evidence
public snapshot- The manifest points to browser-tool entrypoints and has no install lifecycle hook.
- The runtime operation checks cancellation and validates browser launch parameters against the bound profile and browser type.
- The browser process output is captured locally, while tool execution is forwarded to the configured base URL.
- The Chrome helper fetches version information and downloads the requested browser executable.
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.14.
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.14 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.