debugger_enable · CDP-MCP Server MCP: Risk & Policy

WHAT IT DOES

What debugger_enable does on CDP-MCP Server

AI agents invoke debugger_enable to trigger actions in CDP-MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why debugger_enable needs a policy

Enabling the JavaScript debugger activates a debugging subsystem that can intercept execution, pause scripts, and expose internal state. While enabling the debugger itself doesn't execute code or delete data, it triggers an external browser operation that changes the runtime environment and enables further high-risk operations like breakpoints and stack inspection.

From the tool's definition 'Enable the JavaScript debugger for the current target'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

debugger_enable Rate-limited

debugger_enable stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "debugger_enable": {
      "limits": [
        {
          "counter": "debugger_enable_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches CDP-MCP Server, so you can run agents against it safely.

FAQ

Questions about debugger_enable

What does the debugger_enable tool do? +

Enable the JavaScript debugger for the current target. It is categorised as a Execute tool in the CDP-MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on debugger_enable? +

Register the CDP-MCP Server MCP server in PolicyLayer and add a rule for debugger_enable: 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 CDP-MCP Server. Nothing to install.

What risk level is debugger_enable? +

debugger_enable is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit debugger_enable? +

Yes. Add a rate_limit block to the debugger_enable 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.

How do I block debugger_enable completely? +

Set action: deny in the PolicyLayer policy for debugger_enable. 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.

What MCP server provides debugger_enable? +

debugger_enable is provided by the CDP-MCP Server MCP server (jekyll-001/cdp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.