@agimon-ai/po-browse-tool@0.0.0-alpha.82
MCP server for browser automation using Playwright with profile management, page registry, and multi-browser support
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged process and network operations support browser automation and use the Chrome for Testing feed. However, the default MCP logger initializes runtime telemetry unless disabled, and the inspected README does not disclose it; this warrants a warning rather than a block.
Decision evidence
public snapshot- The manifest describes a Playwright browser automation MCP server.
- The telemetry class enables logs unless OTEL_SDK_DISABLED is set and initializes the Node telemetry sink.
- The default MCP logger uses the browse-tool-mcp service name and sends log levels through that telemetry class.
- The server logs tool names and timestamps when handling tool calls; no evidence found that it logs the supplied arguments.
- The Chrome for Testing metadata feed is hosted at googlechromelabs.github.io, consistent with the browser tooling purpose.
- The manifest exposes library entry points and declares no bin command; its purpose is browser automation.
- The process inspection and execution behavior supports browser lifecycle and automation tasks.
- Telemetry destinations are resolved from environment or Agimon configuration rather than a hard-coded unrelated collector.
Source & flagged code
8 flaggedFindings
Affected versions and remediation
This report applies to @agimon-ai/po-browse-tool@0.0.0-alpha.82.
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.82 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.