AI agents invoke nexti 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.
The tool actively executes/advances the target process by one machine instruction in an rr debugging session. It triggers execution of code in the debugged process, which constitutes an Execute action. While it's a controlled single-step in a debugger, it causes the target program to run code and can have side effects depending on what instruction is executed.
From the tool's definition 'Step forward one machine instruction, stepping over call instructions' — this advances execution state in a live debugging session
Attacks that exploit this kind of access
Step forward one machine instruction, stepping over call instructions. 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 nexti: 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.
nexti 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 nexti 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 nexti. 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.
nexti 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 →