registry / @agimon-ai/po-browse-tool / 0.0.0-alpha.9
@agimon-ai/po-browse-tool@0.0.0-alpha.9
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-aiSource inspection shows no install lifecycle hook or concrete attack behavior. The scanner's command-output and network signals correspond to browser setup and local failure diagnostics.
Static reason
One or more suspicious static signals were detected.
Trigger
A user invokes the browser tool or requests browser setup.
Impact
No unconsented data transfer or other harmful effect was established.
Mechanism
The package launches the configured browser, retrieves Chrome for Testing resources from its published feed, and saves captured startup output to a temporary log when startup fails.
AI rationale
Source inspection shows no install lifecycle hook or concrete attack behavior. The scanner's command-output and network signals correspond to browser setup and local failure diagnostics.
Network endpoints1
googlechromelabs.github.io
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest defines browser-tool entrypoints and no install lifecycle hook.
- Both runtime exports require an explicit browser launch request and enforce profile binding.
- Chrome for Testing metadata and downloads are retrieved from the browser vendor's published feed.
- Browser process output is captured for startup-failure diagnostics and written to a temporary launch log; the inspected path does not send it to a remote recipient.
Evidence against
- The flagged command execution launches the configured browser or Docker build; inspected output handling is local diagnostic logging.
- The runtime fetch in the container bridge posts caller-selected tool arguments to its configured local bridge.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShellWebSocket
HighEntropyStrings
Source & flagged code
6 flaggeddist/dockerChromeForTesting-BMmEQq88.mjsView file
1import{t as e}from"./decorateMetadata-D0fK5b4i.mjs";import{t}from"./decorate-B3KLIx2E.mjs";import"reflect-metadata/lite";import{injectable as n}from"inversify";import r,{join as i}...
L2: //# sourceMappingURL=dockerChromeForTesting-BMmEQq88.mjs.map
High
Child Process
Package source references child process execution.
dist/dockerChromeForTesting-BMmEQq88.mjsView on unpkg · L11import{t as e}from"./decorateMetadata-D0fK5b4i.mjs";import{t}from"./decorate-B3KLIx2E.mjs";import"reflect-metadata/lite";import{injectable as n}from"inversify";import r,{join as i}...
L2: //# sourceMappingURL=dockerChromeForTesting-BMmEQq88.mjs.map
High
Same File Env Network Execution
A single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/dockerChromeForTesting-BMmEQq88.mjsView on unpkg · L1dist/extension/background.jsView file
Findings
5 High4 Medium5 Low
HighChild Processdist/dockerChromeForTesting-BMmEQq88.mjs
HighShell
HighSame File Env Network Executiondist/dockerChromeForTesting-BMmEQq88.mjs
HighCommand Output Exfiltrationdist/container-D-D4x8I7.mjs
HighTrigger Reachable Command Output Exfiltrationdist/container-DrE51Rho.cjs
MediumDynamic Requiredist/stubs/playwright-test.cjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowEvaldist/extension/background.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @agimon-ai/po-browse-tool@0.0.0-alpha.9.
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.9 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.