Set a breakpoint to pause execution at a critical line of code. Essential for debugging: pause before potential errors, examine state at decision points, or verify code paths. Breakpoints let you inspect variables and control flow at exact moments.
AI agents use add_breakpoint to create or update resources in DebugMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DebugMCP environment.
Adding a breakpoint creates a new debugging marker in the IDE. This is a reversible write operation (breakpoints can be removed) with minimal blast radius — it only affects the debugging session and does not execute code, delete data, or have financial implications.
From the tool's definition 'Set a breakpoint to pause execution at a critical line of code'
Documented attack patterns abuse exactly the kind of access add_breakpoint gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DebugMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for add_breakpoint:
{
"version": "1",
"default": "deny",
"tools": {
"add_breakpoint": {
"limits": [
{
"counter": "add_breakpoint_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_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.
Free to start. No card required.
Set a breakpoint to pause execution at a critical line of code. Essential for debugging: pause before potential errors, examine state at decision points, or verify code paths. Breakpoints let you inspect variables and control flow at exact moments. It is categorised as a Write tool in the DebugMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Debug MCP server in PolicyLayer and add a rule for add_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 DebugMCP. Nothing to install.
add_breakpoint is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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.
Set action: deny in the PolicyLayer policy for add_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.
add_breakpoint is provided by the Debug MCP server (microsoft/debugmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DebugMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 DebugMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.