@agimon-ai/po-browse-tool@0.0.0-alpha.2
MCP server for browser automation using Playwright with profile management, page registry, and multi-browser support
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the reviewed command and network behavior is tied to browser tooling and explicit spec execution. The scanner signals do not establish a concrete attack.
Decision evidence
public snapshot- package.json lists development and build scripts but no install lifecycle hook.
- Both runtime entrypoints bind page access to the active profile and browser session.
- The Chrome metadata request targets the Chrome for Testing version feed.
- The flagged command execution is exposed through an explicit Playwright spec-running tool.
Source & flagged code
6 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.2.
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.2 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.