Reset RC Method pipeline state. Clears checkpoint store and markdown state file, allowing a fresh rc_start. DESTRUCTIVE - requires explicit confirmation. Use when the user wants to start over or abandon current progress. After success: pipeline is clean, call rc_start or rc_init to begin again.
AI agents call rc_reset to permanently remove resources in RC Engine — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes stored pipeline state, checkpoints, and markdown files without recovery option. While it requires confirmation, the action itself cannot be undone and results in complete loss of work-in-progress data. This is the highest-risk category (Destructive > Execute > Write > Read).
From the tool's definition Tool description explicitly states 'DESTRUCTIVE - requires explicit confirmation' and 'Clears checkpoint store and markdown state file'. It irreversibly removes all pipeline state and progress data.
Attacks that exploit this kind of access
Reset RC Method pipeline state. Clears checkpoint store and markdown state file, allowing a fresh rc_start. DESTRUCTIVE - requires explicit confirmation. Use when the user wants to start over or abandon current progress. After success: pipeline is clean, call rc_start or rc_init to begin again. It is categorised as a Destructive tool in the RC Engine MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the RC Engine MCP server in PolicyLayer and add a rule for rc_reset: 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 RC Engine. Nothing to install.
rc_reset is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the rc_reset 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 rc_reset. 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.
rc_reset is provided by the RC Engine MCP server (originalrashmi/rc-engine-product-framework). 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 →