wasm_agent_state

SERVERClaude Flow SOURCEclaude-flow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/wasm-agent-state.md

WHAT IT DOES

What wasm_agent_state does on Claude Flow

AI agents call wasm_agent_state to retrieve information from Claude Flow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why wasm_agent_state is rated Low

This is a Read operation: it retrieves data (agent state, conversation history, configuration) without modifying or executing anything. However, severity is elevated to 'medium' because access to internal agent state including full message history and configuration could reveal sensitive information (prompts, user data, API keys in context, internal system directives) that an AI might expose or misuse.

From the tool's definition Tool explicitly states 'Read the full internal state' and retrieves 'messages, turn count, config, stop status' from a sandboxed WASM agent—a query operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wasm_agent_state 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_state, this is the rule to start with:

wasm_agent_state Allowed

wasm_agent_state is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wasm_agent_state": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every wasm_agent_state call is checked against it from then on.

FAQ

Questions about wasm_agent_state

What does the wasm_agent_state tool do? +

Read the full internal state of a WASM agent (messages, turn count, config, stop status). Use when native Task is wrong because the agent runs in a sandboxed WASM runtime whose internal conversation history is not directly accessible from the host process. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on wasm_agent_state? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for wasm_agent_state: 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 wasm_agent_state? +

wasm_agent_state is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit wasm_agent_state? +

Yes. Add a rate_limit block to the wasm_agent_state 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 wasm_agent_state completely? +

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

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

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 496 Claude Flow tools →

Across the catalogue

get_agent on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →