autopilot_reset
Reset autopilot iteration counter and restart the timer. Use when running long-horizon goals that should resume automatically across sessions — Claude Code has no native autonomous-loop scheduler. Pair with autopilot_enable + a goal description, then let cron fires advance the work. For interacti...
This record as markdown: /tools/io-github-ruvnet-claude-flow/autopilot-reset.md
What autopilot_reset does on Claude Flow
AI agents call autopilot_reset to permanently remove resources in Claude Flow, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why autopilot_reset is rated Critical
An AI agent that decides to call autopilot_reset doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Claude Flow is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs autopilot_reset safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For autopilot_reset, this is the rule to start with:
autopilot_reset is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every autopilot_reset call is checked against it from then on.
Questions about autopilot_reset
Reset autopilot iteration counter and restart the timer. Use when running long-horizon goals that should resume automatically across sessions — Claude Code has no native autonomous-loop scheduler. Pair with autopilot_enable + a goal description, then let cron fires advance the work. For interactive single-task sessions, native Task is fine. It is categorised as a Destructive tool in the Claude Flow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Claude Flow MCP server in PolicyLayer and add a rule for autopilot_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 Claude Flow. Nothing to install.
autopilot_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 autopilot_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 autopilot_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.
autopilot_reset is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Flow, and thousands of servers like it.
Across the catalogue