wasm_agent_is_stopped
Check whether a WASM agent has reached its stop condition (max turns or explicit stop). Use when native Task is wrong because the stop condition is evaluated inside the WASM runtime and not observable from the host without an explicit query.
This record as markdown: /tools/io-github-ruvnet-claude-flow/wasm-agent-is-stopped.md
What wasm_agent_is_stopped does on Claude Flow
AI agents call wasm_agent_is_stopped 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.
Why wasm_agent_is_stopped is rated Low
This tool performs a read-only check of agent status within a WASM runtime. It retrieves information about whether a stop condition has been met, with no side effects, state modifications, or external operations triggered. The explicit mention of checking/querying status confirms the Read category.
From the tool's definition Tool name 'is_stopped' and description 'Check whether a WASM agent has reached its stop condition' indicate a query operation that retrieves status without modifying state.
Attacks that exploit this kind of access
The rule that runs wasm_agent_is_stopped 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_is_stopped, this is the rule to start with:
wasm_agent_is_stopped is read-only, so it stays allowed. 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_is_stopped call is checked against it from then on.
Questions about wasm_agent_is_stopped
Check whether a WASM agent has reached its stop condition (max turns or explicit stop). Use when native Task is wrong because the stop condition is evaluated inside the WASM runtime and not observable from the host without an explicit query. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.
Register the Claude Flow MCP server in PolicyLayer and add a rule for wasm_agent_is_stopped: 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_is_stopped is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the wasm_agent_is_stopped 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_is_stopped. 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_is_stopped 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