remove_breakpoint · MCP JS Debugger MCP: Risk & Policy

WHAT IT DOES

What remove_breakpoint does on MCP JS Debugger

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

WHY IT NEEDS A POLICY

Why remove_breakpoint needs a policy

Removing a breakpoint modifies the debugger's configuration state, but this is a reversible action (breakpoints can be re-added). It does not delete code, data, or execute arbitrary commands. The blast radius is low since misuse only affects debugging sessions, not production data or systems.

From the tool's definition 'Removes a previously set breakpoint' - modifies debugger state by deleting a breakpoint configuration

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remove_breakpoint Rate-limited

remove_breakpoint 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": {
    "remove_breakpoint": {
      "limits": [
        {
          "counter": "remove_breakpoint_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 JS Debugger, so you can run agents against it safely.

FAQ

Questions about remove_breakpoint

What does the remove_breakpoint tool do? +

Removes a previously set breakpoint. Use list_breakpoints to find breakpoint IDs. It is categorised as a Write tool in the MCP JS Debugger MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on remove_breakpoint? +

Register the MCP JS Debugger MCP server in PolicyLayer and add a rule for remove_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 MCP JS Debugger. Nothing to install.

What risk level is remove_breakpoint? +

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

Can I rate-limit remove_breakpoint? +

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

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

remove_breakpoint is provided by the MCP JS Debugger MCP server (johngrimes/mcp-js-debugger). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

remove_breakpoint is one line of MCP JS Debugger's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →