debug_clearBreakpoints

THE RISK

Critical Risk

Why debug_clearBreakpoints needs a policy

This tool permanently removes all breakpoints from the workspace in a single operation. While breakpoints are debugging aids rather than data, bulk-clearing them all at once cannot be automatically undone and would require manual effort to restore, making it Destructive. The blast radius is medium since it only affects debugging configuration, not source code or data.

From the tool's definition 'Remove all breakpoints from the workspace' — bulk removal of all breakpoints is irreversible without manual re-entry

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

POLICY

How to control debug_clearBreakpoints

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_clearBreakpoints:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "debug_clearBreakpoints"
  ]
}

debug_clearBreakpoints disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

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.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP Server for VS Code tools

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 Execute debug_stepOut Step out of the current function and return to the caller

All 25 MCP Server for VS Code tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in MCP Server for VS Code → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about debug_clearBreakpoints

What does the debug_clearBreakpoints tool do? +

Remove all breakpoints from the workspace. It is categorised as a Destructive tool in the MCP Server for VS Code MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on debug_clearBreakpoints? +

Register the MCP Server for VS Code MCP server in PolicyLayer and add a rule for debug_clearBreakpoints: 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_clearBreakpoints? +

debug_clearBreakpoints is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit debug_clearBreakpoints? +

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

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

debug_clearBreakpoints 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 →