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.
This record as markdown: /tools/ruflo/system-reset.md
What system_reset does on Ruflo
AI agents call system_reset to permanently remove resources in Ruflo, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why system_reset is rated Critical
A system reset irreversibly wipes or reinitializes the runtime state of the entire Ruflo daemon, including memory indexes (HNSW), reasoning banks, swarm coordination state, and circuit breaker status. This cannot be undone and would destroy all in-flight agent workflows, learned memory, and swarm intelligence state. The blast radius is critical as it affects the entire multi-agent system simultaneously.
From the tool's definition Reset system state — resets HNSW index size, ReasoningBank state, swarm health, breaker status in the running daemon
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs system_reset safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For system_reset, this is the rule to start with:
system_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 Ruflo, apply this rule, and every system_reset call is checked against it from then on.
Questions about 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. It is categorised as a Destructive tool in the Ruflo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ruflo 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 Ruflo. Nothing to install.
system_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 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.
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.
system_reset is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ruflo, and thousands of servers like it.
Across the catalogue