Return structured errors captured from the Next.js dev server (compile, module-not-found, runtime, hydration). Pass
AI agents call get_errors to retrieve information from Nextjs Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves diagnostic error information (compile, module-not-found, runtime, hydration errors) from a running Next.js application. It is a read-only operation that has no side effects, does not modify any data, and does not execute code or trigger external operations. The blast radius if misused is minimal—an AI agent could only gain visibility into errors the app is already experiencing.
From the tool's definition Tool name is 'get_errors' and description states 'Return structured errors' — retrieves and queries error data from the Next.js dev server with no modification or side effects.
Attacks that exploit this kind of access
Return structured errors captured from the Next.js dev server (compile, module-not-found, runtime, hydration). Pass. It is categorised as a Read tool in the Nextjs Agent MCP Server, which means it retrieves data without modifying state.
Register the Nextjs Agent MCP server in PolicyLayer and add a rule for get_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 Nextjs Agent. Nothing to install.
get_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 get_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 get_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.
get_errors is provided by the Nextjs Agent MCP server (zohaib3249/nextjs-agent-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 →