AI agents call clear_error_history to permanently remove resources in DevServer MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data (error history) that cannot be recovered. While the blast radius is limited to development logs rather than production data, the irreversible deletion of records qualifies it as Destructive rather than Write. Severity is high because an agent clearing error history could obscure debugging information, mask recurring issues, or erase evidence of problems that need investigation.
From the tool's definition Tool description explicitly states 'Clear all stored error history' — this irreversibly deletes accumulated error records with no undo mechanism.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access clear_error_history 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 clear_error_history:
{
"version": "1",
"default": "deny",
"hide": [
"clear_error_history"
]
}clear_error_history disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Clear all stored error history. It is categorised as a Destructive tool in the DevServer MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the DevServer MCP server in PolicyLayer and add a rule for clear_error_history: 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.
clear_error_history is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_error_history 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 clear_error_history. 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.
clear_error_history 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.