This record as markdown: /tools/io-github-ruvnet-claude-flow/wasm-agent-export.md
What wasm_agent_export does on Claude Flow
AI agents use wasm_agent_export to create or update resources in Claude Flow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Flow environment.
Why wasm_agent_export is rated Medium
This tool creates/serializes and extracts a WASM agent, which is a reversible data creation/modification action. It does not delete data (not Destructive), does not directly move money (not Financial), and does not execute arbitrary code or shell commands at runtime (not Execute in the sense of triggering external side effects).
From the tool's definition Tool name is 'wasm_agent_export' and description states 'Export a WASM agent'. Export operations create or extract artifacts (in this case, serialized WASM agent code/state) that are then stored or transmitted.
Attacks that exploit this kind of access
The rule that runs wasm_agent_export 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 wasm_agent_export, this is the rule to start with:
wasm_agent_export stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every wasm_agent_export call is checked against it from then on.
Questions about wasm_agent_export
Export a WASM agent\. It is categorised as a Write tool in the Claude Flow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Flow MCP server in PolicyLayer and add a rule for wasm_agent_export: 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.
wasm_agent_export is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the wasm_agent_export 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_export. 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_export 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.
This server
Across the catalogue