gt_wasm_optimize_convoy · Claude Flow MCP: Risk & Policy

WHAT IT DOES

What gt_wasm_optimize_convoy does on Claude Flow

AI agents invoke gt_wasm_optimize_convoy to trigger actions in Claude Flow. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why gt_wasm_optimize_convoy needs a policy

The tool executes WebAssembly graph algorithms to optimize convoy execution ordering. Running WASM code constitutes an Execute-class action since it triggers external computation whose effects depend on the convoy configuration passed in.

From the tool's definition 'Optimize convoy execution order using WASM graph algorithms' — runs WASM (WebAssembly) code to process and reorder execution sequences

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gt_wasm_optimize_convoy Rate-limited

gt_wasm_optimize_convoy stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gt_wasm_optimize_convoy": {
      "limits": [
        {
          "counter": "gt_wasm_optimize_convoy_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 gt_wasm_optimize_convoy

What does the gt_wasm_optimize_convoy tool do? +

Optimize convoy execution order using WASM graph algorithms. It is categorised as a Execute tool in the Claude Flow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on gt_wasm_optimize_convoy? +

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

gt_wasm_optimize_convoy is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit gt_wasm_optimize_convoy? +

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

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

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