Get captured debugger pause/resume events (paginated: omit offset/limit to return everything; default offset=0)
AI agents call getDebuggerEvents to retrieve information from MCP Chrome Debugger Protocol without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical debugger events from an attached Node.js process. It performs no mutation or side effects on the debugger state or application. However, the severity is elevated to 'medium' because access to debugger events could expose sensitive information about application execution flow, variable values, call stacks, and business logic that would be valuable to an attacker, even though the…
From the tool's definition Tool description states 'Get captured debugger pause/resume events (paginated: omit offset/limit to return everything; default offset=0)' — the word 'Get' and retrieval of event logs indicates read-only data retrieval without modification.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get captured debugger pause/resume events (paginated: omit offset/limit to return everything; default offset=0). It is categorised as a Read tool in the MCP Chrome Debugger Protocol MCP Server, which means it retrieves data without modifying state.
Register the MCP Chrome Debugger Protocol MCP server in PolicyLayer and add a rule for getDebuggerEvents: 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.
getDebuggerEvents 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 getDebuggerEvents 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 getDebuggerEvents. 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.
getDebuggerEvents 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 →