gt_wasm_cook_batch · Ruflo MCP: Risk & Policy

WHAT IT DOES

What gt_wasm_cook_batch does on Ruflo

AI agents invoke gt_wasm_cook_batch to trigger actions in Ruflo. 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_cook_batch needs a policy

The tool executes WASM (WebAssembly) code to process multiple formulas in batch. Running arbitrary compiled code (WASM) constitutes code execution, with potentially broad side effects depending on the formulas. In a multi-agent swarm harness context, batch execution of WASM formulas carries high blast radius if misused, as it could trigger downstream agent workflows or data transformations at scale.

From the tool's definition 'cook' multiple formulas using WASM — executing compiled WebAssembly code to process/evaluate a batch of formulas

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gt_wasm_cook_batch Rate-limited

gt_wasm_cook_batch 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_cook_batch": {
      "limits": [
        {
          "counter": "gt_wasm_cook_batch_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 Ruflo, so you can run agents against it safely.

FAQ

Questions about gt_wasm_cook_batch

What does the gt_wasm_cook_batch tool do? +

Batch cook multiple formulas using WASM for maximum performance. It is categorised as a Execute tool in the Ruflo 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_cook_batch? +

Register the Ruflo MCP server in PolicyLayer and add a rule for gt_wasm_cook_batch: 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 Ruflo. Nothing to install.

What risk level is gt_wasm_cook_batch? +

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

Can I rate-limit gt_wasm_cook_batch? +

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

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

gt_wasm_cook_batch is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.