AI agents invoke reverse_stepi 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.
This tool executes a reverse debugger operation that steps backward one machine instruction in a running debug session. It triggers an external operation (controlling execution flow of a debugged process) whose effects depend on the current debugging context. While it doesn't delete data or move money, it actively manipulates process execution state, placing it in the Execute category.
From the tool's definition Step backward one machine instruction. Reverse counterpart of stepi.
Attacks that exploit this kind of access
Step backward one machine instruction. Reverse counterpart of stepi. 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 reverse_stepi: 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.
reverse_stepi 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 reverse_stepi 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 reverse_stepi. 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.
reverse_stepi 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 →