debugger_set_breakpoint · CDP-MCP Server MCP: Risk & Policy

WHAT IT DOES

What debugger_set_breakpoint does on CDP-MCP Server

AI agents invoke debugger_set_breakpoint 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_breakpoint needs a policy

Setting a breakpoint modifies the browser debugger state and causes the browser to pause execution when the breakpoint is hit, triggering external side effects in the debugging session. It's not purely a read operation, and it's not destructive or financial. It falls under Execute because it actively intervenes in the browser's execution flow, potentially halting scripts and affecting application behavior.

From the tool's definition Set a breakpoint at a URL and line number

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

debugger_set_breakpoint Rate-limited

debugger_set_breakpoint 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_breakpoint": {
      "limits": [
        {
          "counter": "debugger_set_breakpoint_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_breakpoint

What does the debugger_set_breakpoint tool do? +

Set a breakpoint at a URL and line number (1-based). Use urlRegex for pattern matching. 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_breakpoint? +

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

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

Can I rate-limit debugger_set_breakpoint? +

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

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

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