AI agents call inspect_network_errors to retrieve information from Tscafejr without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool passively observes and reports existing system state (console errors, exceptions, network failures). It does not execute arbitrary code, modify data, delete resources, or trigger external operations—it only reads diagnostic outputs that have already occurred.
From the tool's definition The tool 'inspect_network_errors' captures and retrieves diagnostic information: console logs, uncaught exceptions, and HTTP error responses. The verb 'captures' indicates data collection without modification or execution of side effects.
Attacks that exploit this kind of access
Captures console logs (errors/warns), uncaught JS exceptions, and 4xx/5xx network failures. It is categorised as a Read tool in the Tscafejr MCP Server, which means it retrieves data without modifying state.
Register the Tscafejr MCP server in PolicyLayer and add a rule for inspect_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 Tscafejr. Nothing to install.
inspect_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 inspect_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 inspect_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.
inspect_network_errors is provided by the Tscafejr MCP server (tscafejr/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 →