AI agents invoke breakpoint_set to trigger actions in Rr. 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 registering a trigger that pauses execution at a specified location. This is an active operation that affects program execution flow within the rr debugging environment. It's not purely read-only, and while reversible (breakpoints can be deleted), its primary function is to control/interrupt execution, placing it in the Execute category.
From the tool's definition Set a breakpoint to pause execution at a specific
Attacks that exploit this kind of access
Set a breakpoint to pause execution at a specific. It is categorised as a Execute tool in the Rr MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Rr MCP server in PolicyLayer and add a rule for breakpoint_set: 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 Rr. Nothing to install.
breakpoint_set 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_set 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_set. 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_set is provided by the Rr MCP server (jnjaeschke/rr-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 →