wasm_agent_reset
Reset a WASM agent — clears messages and turn count so it can be reused across tasks. Use when native Task is wrong because the agent lives in a sandboxed WASM runtime that must be explicitly reset rather than simply re-spawned.
This record as markdown: /tools/ruflo/wasm-agent-reset.md
What wasm_agent_reset does on Ruflo
AI agents call wasm_agent_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 wasm_agent_reset is rated Critical
Resetting a WASM agent irreversibly clears its message history and turn count. This data cannot be recovered once wiped, making it a destructive operation. The blast radius is high because an agent misuse could destroy context/state accumulated over an entire workflow, potentially breaking dependent tasks in a multi-agent swarm.
From the tool's definition clears messages and turn count
Attacks that exploit this kind of access
The rule that runs wasm_agent_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 wasm_agent_reset, this is the rule to start with:
wasm_agent_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 wasm_agent_reset call is checked against it from then on.
Questions about wasm_agent_reset
Reset a WASM agent — clears messages and turn count so it can be reused across tasks. Use when native Task is wrong because the agent lives in a sandboxed WASM runtime that must be explicitly reset rather than simply re-spawned. 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 wasm_agent_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.
wasm_agent_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 wasm_agent_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 wasm_agent_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.
wasm_agent_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