wasm_agent_todos

Get the structured todo list of a WASM agent as JSON. Use when native Task is wrong because the todo state lives inside the sandboxed WASM runtime and is not visible to the host process.

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-todos.md

WHAT IT DOES

What wasm_agent_todos does on Claude Flow

AI agents call wasm_agent_todos 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_todos is rated Low

This tool performs data retrieval from a sandboxed WASM runtime with no side effects. It queries the internal state of a WASM agent and returns structured data (JSON), which is characteristic of a Read operation. The sandboxed context mitigates risk further, as the tool cannot modify, execute, or delete anything.

From the tool's definition The tool description explicitly states it 'Get[s] the structured todo list of a WASM agent as JSON', indicating a retrieval operation. No modification, deletion, or execution capabilities are mentioned.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

wasm_agent_todos Allowed

wasm_agent_todos 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_todos": {}
  }
}

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_todos call is checked against it from then on.

FAQ

Questions about wasm_agent_todos

What does the wasm_agent_todos tool do? +

Get the structured todo list of a WASM agent as JSON. Use when native Task is wrong because the todo state lives inside the sandboxed WASM runtime and is not visible to 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_todos? +

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

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

Can I rate-limit wasm_agent_todos? +

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

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

wasm_agent_todos 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 →