New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

gt_wasm_cook_batch

Batch cook multiple formulas using WASM for maximum performance

SERVERClaude Flow SOURCEclaude-flow
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/gt-wasm-cook-batch.md

What gt_wasm_cook_batch does on Claude Flow

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.

Why gt_wasm_cook_batch is rated High

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

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 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_cook_batch? +

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.

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Claude Flow's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.