wasm_agent_terminate

Server Claude Flow claude-flow

Category Write

Risk class Medium

Parameters 00 required

WHAT IT DOES

What wasm_agent_terminate does on Claude Flow

AI agents use wasm_agent_terminate 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 IT NEEDS A POLICY

Why wasm_agent_terminate needs a policy

An AI agent can call wasm_agent_terminate faster than any human can review — one bad instruction and it creates or modifies resources in Claude Flow by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wasm_agent_terminate Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wasm_agent_terminate": {
      "limits": [
        {
          "counter": "wasm_agent_terminate_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Claude Flow, so you can run agents against it safely.

FAQ

Questions about wasm_agent_terminate

What does the wasm_agent_terminate tool do? +

Terminate a WASM agent and free resources. Use when native Task is wrong because the workload needs sandboxed isolation — untrusted code execution, browser-side run, deterministic replay. Pair with wasm_gallery_search to find a published agent, or wasm_agent_create to scaffold a fresh one. For trusted in-process work, native Task is fine. 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.

How do I enforce a policy on wasm_agent_terminate? +

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

wasm_agent_terminate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit wasm_agent_terminate? +

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

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

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