Return captured network request failures (404s, CORS errors, etc.).
AI agents call browser_network_errors to retrieve information from Taw Computer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves already-captured network error data. It has no side effects, does not modify any state, and simply returns diagnostic information about failed network requests.
From the tool's definition Return captured network request failures (404s, CORS errors, etc.)
Documented attack patterns abuse exactly the kind of access browser_network_errors gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Taw Computer, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_network_errors:
{
"version": "1",
"default": "deny",
"tools": {
"browser_network_errors": {}
}
}browser_network_errors is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Return captured network request failures (404s, CORS errors, etc.). It is categorised as a Read tool in the Taw Computer MCP Server, which means it retrieves data without modifying state.
Register the Taw Computer MCP server in PolicyLayer and add a rule for browser_network_errors: 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 Taw Computer. Nothing to install.
browser_network_errors 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 browser_network_errors 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 browser_network_errors. 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.
browser_network_errors is provided by the Taw Computer MCP server (tawgroup/taw-computer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Taw Computer, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
36 Taw Computer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.