Check our network ERROR logs
AI agents call getNetworkErrors to retrieve information from BrowserTools MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing network error logs from the browser's network activity history. It is a passive read operation that captures and analyzes data without creating, modifying, or deleting any state. The blast radius is minimal—an AI agent misusing this would gain visibility into network failures but cannot alter system behavior, execute commands, or trigger external operations.
From the tool's definition Tool name 'getNetworkErrors' and description 'Check our network ERROR logs' indicate retrieval of logged data with no modification or side effects.
Attacks that exploit this kind of access
Check our network ERROR logs. It is categorised as a Read tool in the BrowserTools MCP MCP Server, which means it retrieves data without modifying state.
Register the BrowserTools MCP server in PolicyLayer and add a rule for getNetworkErrors: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches BrowserTools MCP. Nothing to install.
getNetworkErrors is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getNetworkErrors rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for getNetworkErrors. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
getNetworkErrors is provided by the BrowserTools MCP server (oenius/browser-tools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →