gt_formula_cook
Cook a formula into a protomolecule with variable substitution (WASM accelerated)
This record as markdown: /tools/ruflo/gt-formula-cook.md
What gt_formula_cook does on Ruflo
AI agents invoke gt_formula_cook 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 gt_formula_cook is rated High
The tool 'cooks' (compiles/transforms) a formula using WASM execution, indicating it runs code or a computation engine. Variable substitution and WASM acceleration suggest active execution of logic rather than a simple read or write.
From the tool's definition 'Cook a formula into a protomolecule with variable substitution (WASM accelerated)' — executes a WASM-accelerated compilation/transformation process
Attacks that exploit this kind of access
The rule that runs gt_formula_cook safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gt_formula_cook, this is the rule to start with:
gt_formula_cook 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every gt_formula_cook call is checked against it from then on.
Questions about gt_formula_cook
Cook a formula into a protomolecule with variable substitution (WASM accelerated). 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.
Register the Ruflo 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 Ruflo. 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 Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ruflo, and thousands of servers like it.
Across the catalogue