@agimon-ai/po-browse-tool@0.0.0-alpha.47
MCP server for browser automation using Playwright with profile management, page registry, and multi-browser support
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource inspection resolved the command-execution and dynamic-code signals to browser and custom-tool functionality. The package manifest has no install lifecycle hook, and the inspected entrypoints did not establish a concrete attack path.
Decision evidence
public snapshot- package.json points to the CommonJS and ESM browser-tool entrypoints; its scripts show build tasks, with no install lifecycle hook.
- Both entrypoints bind browser operations to a runtime profile and browser instance.
- The inspected port-registry dependency exposes port-allocation APIs through its entrypoints.
- The inspected process-registry dependency handles process lifecycle cleanup through its entrypoints.
- The inspected validator dependency uses Zod for schema validation.
- Process spawning serves browser launch and configured server operation; the dynamic code path is part of the browser tool’s custom-code feature.
Source & flagged code
8 flaggedFindings
Affected versions and remediation
This report applies to @agimon-ai/po-browse-tool@0.0.0-alpha.47.
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.47 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.