debug_setBreakpoint

THE RISK

Medium Risk

Why debug_setBreakpoint needs a policy

Setting a breakpoint is a reversible write operation that modifies debug configuration state. It does not execute code, delete data, or have financial implications. Breakpoints can be cleared/removed, making this fully reversible. The blast radius is low since misuse merely adds debug pause points.

From the tool's definition 'Set a breakpoint by symbol name or file/line with optional conditions'

Documented attack patterns abuse exactly the kind of access debug_setBreakpoint gives an agent:

POLICY

How to control debug_setBreakpoint

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server for VS Code, and nothing reaches the server without passing your rules. This is the rule we recommend for debug_setBreakpoint:

policy.json

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

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

Create a free account and register MCP Server for VS Code — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP Server for VS Code tools

Destructive debug_clearBreakpoints Remove all breakpoints from the workspace Execute debug_evaluateExpression Evaluate an expression in the current debug context (REPL/watch functionality). Test hypot Execute debug_startSession Start a debug session using a configuration from launch.json. Launch debugging instantly - Execute debug_stepOver Step over the current line of code (execute current line without entering functions) Execute debug_stopSession Stop the current debug session Execute debug_continueExecution Continue execution from the current breakpoint or paused state Execute debug_pauseExecution Pause the running debug session at the current execution point Execute debug_stepInto Step into function calls on the current line

All 25 MCP Server for VS Code tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about debug_setBreakpoint

What does the debug_setBreakpoint tool do? +

Set a breakpoint by symbol name or file/line with optional conditions. Debug smarter - set breakpoints instantly without clicking through files. It is categorised as a Write tool in the MCP Server for VS Code MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on debug_setBreakpoint? +

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

What risk level is debug_setBreakpoint? +

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

Can I rate-limit debug_setBreakpoint? +

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

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

debug_setBreakpoint is provided by the MCP Server for VS Code MCP server (malvex/mcp-server-vscode). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Server for VS Code tool call.

Start from MCP Server for VS Code, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →