Set a breakpoint. Triggers in both directions in rr sessions.
AI agents invoke breakpoint to trigger actions in gdb and rr Debugging. 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 state of a debugging session by inserting an interrupt into the execution flow of a program. This is an active operation that affects program execution behavior, not merely reading data. It operates within a debugger that can run programs and execute code, making it an Execute-category action.
From the tool's definition Set a breakpoint. Triggers in both directions in rr sessions.
Attacks that exploit this kind of access
Set a breakpoint. Triggers in both directions in rr sessions. It is categorised as a Execute tool in the gdb and rr Debugging MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the gdb and rr Debugging MCP server in PolicyLayer and add a rule for 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 gdb and rr Debugging. Nothing to install.
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 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 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.
breakpoint is provided by the gdb and rr Debugging MCP server (schuay/gdb-mcp). 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 →