Batch cook multiple formulas using WASM for maximum performance
AI agents invoke gt_wasm_cook_batch 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.
This tool runs WebAssembly (WASM) code to evaluate/execute multiple formulas in batch. Executing WASM constitutes code execution with potentially broad side effects depending on formula content. The batch nature amplifies blast radius.
From the tool's definition "Batch cook multiple formulas using WASM" — executes WASM (WebAssembly) code to process multiple formulas in batch
Attacks that exploit this kind of access
Batch cook multiple formulas using WASM for maximum performance. 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.
Register the Claude Flow 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 Claude Flow. Nothing to install.
gt_wasm_cook_batch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
gt_wasm_cook_batch 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.