Get current debugger connection state and tool availability
AI agents call getDebuggerState 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 and queries the current state of the debugger connection and available tools. It has no side effects, does not execute code, does not modify data, and does not delete anything. It is purely informational, making it a Read category tool with low severity since it only exposes connection metadata.
From the tool's definition Tool name 'getDebuggerState' and description 'Get current debugger connection state and tool availability' indicate a read-only query operation that retrieves state information without modification or execution of code.
Attacks that exploit this kind of access
Get current debugger connection state and tool availability. 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 getDebuggerState: 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.
getDebuggerState 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 getDebuggerState 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 getDebuggerState. 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.
getDebuggerState 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 →