Get a comprehensive summary of all detected errors
AI agents call get_error_summary to retrieve information from DevServer 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 summarizes error information from development server logs. It performs no write, delete, or execute operations; it only queries and presents existing error data. The sibling tools (clear_error_history, watch_for_errors) confirm this is a read-only information retrieval function.
From the tool's definition Tool name is 'get_error_summary' and description states 'Get a comprehensive summary of all detected errors' — purely retrieval of aggregated error data with no modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access get_error_summary gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DevServer MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_error_summary:
{
"version": "1",
"default": "deny",
"tools": {
"get_error_summary": {}
}
}get_error_summary 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.
Get a comprehensive summary of all detected errors. It is categorised as a Read tool in the DevServer MCP MCP Server, which means it retrieves data without modifying state.
Register the DevServer MCP server in PolicyLayer and add a rule for get_error_summary: 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 DevServer MCP. Nothing to install.
get_error_summary 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_error_summary 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_error_summary. 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_error_summary is provided by the DevServer MCP server (mntlabs/devserver-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DevServer MCP, 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.
7 DevServer MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.