setBreakpointsBatch · MCP Chrome Debugger Protocol MCP

WHAT IT DOES

What setBreakpointsBatch does on MCP Chrome Debugger Protocol

AI agents use setBreakpointsBatch to create or update resources in MCP Chrome Debugger Protocol — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Chrome Debugger Protocol environment.

WHY IT NEEDS A POLICY

Why setBreakpointsBatch needs a policy

This tool sets (creates/writes) breakpoints in a debugger session. It modifies debugger state by adding breakpoints across multiple files, but does not execute code, delete data, or have financial implications. Breakpoints are reversible debug configurations, making this a Write-category action with low severity since misuse at worst causes unintended pauses in a debugging session.

From the tool's definition Set breakpoints across multiple source files in a single call... same source-map resolution and tracking as setBreakpoints

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

setBreakpointsBatch Rate-limited

setBreakpointsBatch stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "setBreakpointsBatch": {
      "limits": [
        {
          "counter": "setbreakpointsbatch_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about setBreakpointsBatch

What does the setBreakpointsBatch tool do? +

Set breakpoints across multiple source files in a single call. Each file entry is processed in parallel (capped at 4 concurrent files) using the same source-map resolution and tracking as setBreakpoints. Failures in one file do not block the others; per-file outcomes are returned alongside a summary tally. Use this on session start to seed many breakpoints faster than sequential setBreakpoints calls. It is categorised as a Write tool in the MCP Chrome Debugger Protocol MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on setBreakpointsBatch? +

Register the MCP Chrome Debugger Protocol MCP server in PolicyLayer and add a rule for setBreakpointsBatch: 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.

What risk level is setBreakpointsBatch? +

setBreakpointsBatch is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit setBreakpointsBatch? +

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

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

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