debugger_set_exception_breakpoints

WHAT IT DOES

What debugger_set_exception_breakpoints does on CDP-MCP Server

AI agents invoke debugger_set_exception_breakpoints 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_set_exception_breakpoints needs a policy

Setting exception breakpoints modifies the runtime behavior of the debugger, causing the browser to pause execution when exceptions occur. This is an Execute-category action because it triggers external operational changes (pausing/resuming browser execution) rather than simply reading state or creating/modifying persistent data.

From the tool's definition Configure when to pause on exceptions — this controls debugger breakpoint behavior, affecting execution flow in the browser debugging session

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

debugger_set_exception_breakpoints Rate-limited

debugger_set_exception_breakpoints 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_set_exception_breakpoints": {
      "limits": [
        {
          "counter": "debugger_set_exception_breakpoints_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_set_exception_breakpoints

What does the debugger_set_exception_breakpoints tool do? +

Configure when to pause on exceptions. 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_set_exception_breakpoints? +

Register the CDP-MCP Server MCP server in PolicyLayer and add a rule for debugger_set_exception_breakpoints: 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_set_exception_breakpoints? +

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

Can I rate-limit debugger_set_exception_breakpoints? +

Yes. Add a rate_limit block to the debugger_set_exception_breakpoints 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_set_exception_breakpoints completely? +

Set action: deny in the PolicyLayer policy for debugger_set_exception_breakpoints. 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_set_exception_breakpoints? +

debugger_set_exception_breakpoints 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.