Clear all captured debugger events from memory
AI agents call clearDebuggerEvents to permanently remove resources in MCP Chrome Debugger Protocol — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes captured debugger event history from memory. Once cleared, those events cannot be recovered, making it a destructive action. While the blast radius is limited to debugging data rather than production data, the operation cannot be undone, justifying the Destructive classification at medium severity.
From the tool's definition 'Clear all captured debugger events from memory'
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear all captured debugger events from memory. It is categorised as a Destructive tool in the MCP Chrome Debugger Protocol MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Chrome Debugger Protocol MCP server in PolicyLayer and add a rule for clearDebuggerEvents: 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 MCP Chrome Debugger Protocol. Nothing to install.
clearDebuggerEvents 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 clearDebuggerEvents 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 clearDebuggerEvents. 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.
clearDebuggerEvents is provided by the MCP Chrome Debugger Protocol MCP server (vitalyostanin/mcp-chrome-debugger-protocol). 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 →