Cook a formula into a protomolecule with variable substitution (WASM accelerated)
AI agents invoke gt_formula_cook 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.
The tool 'cooks' (compiles/transforms) a formula using WebAssembly acceleration with variable substitution. This implies executing a computation or code-transformation pipeline, likely producing an artifact (a 'protomolecule'). WASM execution with variable substitution can have significant side effects depending on what the formula contains.
From the tool's definition 'Cook a formula into a protomolecule with variable substitution (WASM accelerated)' — involves executing a WASM-accelerated compilation/transformation process
Attacks that exploit this kind of access
Cook a formula into a protomolecule with variable substitution (WASM accelerated). 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_formula_cook: 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_formula_cook 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_formula_cook 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_formula_cook. 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_formula_cook 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.