system_reset

Reset system state Use when native Bash is wrong because you need Ruflo runtime metrics (HNSW index size, ReasoningBank state, swarm health, breaker status) — those are not in /proc, only in the running daemon. For OS-level info (uptime, disk, mem), native Bash + standard tools are fine.

Server Claude Flow claude-flow
Category Destructive
Risk class Critical
Parameters 00 required

What system_reset does on Claude Flow

AI agents call system_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 system_reset needs a policy

A system reset that wipes or reinitializes live daemon state (neural indices, reasoning banks, swarm configurations, circuit breaker states) is effectively irreversible without a prior snapshot or backup.

From the tool's definition 'Reset system state' — resetting system state implies irreversible clearing of runtime state including HNSW index size, ReasoningBank state, swarm health, and breaker status in the running daemon

Risk signalsAdmin/system-level operation

Questions about system_reset

What does the system_reset tool do? +

Reset system state Use when native Bash is wrong because you need Ruflo runtime metrics (HNSW index size, ReasoningBank state, swarm health, breaker status) — those are not in /proc, only in the running daemon. For OS-level info (uptime, disk, mem), native Bash + standard tools are 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.

How do I enforce a policy on system_reset? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for system_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.

What risk level is system_reset? +

system_reset is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit system_reset? +

Yes. Add a rate_limit block to the system_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.

How do I block system_reset completely? +

Set action: deny in the PolicyLayer policy for system_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.

What MCP server provides system_reset? +

system_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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.