Set breakpoint at address or symbol
AI agents invoke set_breakpoint to trigger actions in MCP Debug Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Setting a breakpoint modifies the runtime behavior of an attached process by inserting a trap/interrupt at a specified address or symbol. This is an active operation that affects process execution flow, classifying it as Execute. The blast radius is medium since it can halt or disrupt a running process, but does not by itself destroy data or move money.
From the tool's definition 'Set breakpoint at address or symbol' — sets a breakpoint which modifies the debugging state of a live process and controls execution flow
Attacks that exploit this kind of access
Set breakpoint at address or symbol. It is categorised as a Execute tool in the MCP Debug Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Debug Server MCP server in PolicyLayer and add a rule for set_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 Debug Server. Nothing to install.
set_breakpoint is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the set_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 set_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.
set_breakpoint is provided by the MCP Debug Server MCP server (nickzer0/mcp-debugserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →