gt_wasm_parse_formula

Parse TOML formula content to AST using WASM (352x faster than JavaScript)

Server Ruflo ruvnet/ruflo
Category Execute
Risk class High
Parameters 00 required

What gt_wasm_parse_formula does on Ruflo

AI agents invoke gt_wasm_parse_formula 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_wasm_parse_formula needs a policy

Although 'parse' might initially suggest a Read operation, parsing formulas (especially those in TOML format destined for multi-agent swarms in a meta-harness context) is fundamentally an Execute category action. Parsing formulas can materialize executable code structures. In a system deploying autonomous agent swarms, a maliciously crafted formula could enable code injection.

From the tool's definition The tool parses TOML formula content to an AST using WebAssembly. Parsing untrusted formula content to an AST is an Execute operation because it can trigger code evaluation, transformation, or execution logic downstream.

Questions about gt_wasm_parse_formula

What does the gt_wasm_parse_formula tool do? +

Parse TOML formula content to AST using WASM (352x faster than JavaScript). 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_parse_formula? +

Register the Ruflo MCP server in PolicyLayer and add a rule for gt_wasm_parse_formula: 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_parse_formula? +

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

Can I rate-limit gt_wasm_parse_formula? +

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

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

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

// THE FULL RECORD

gt_wasm_parse_formula is one line of Ruflo's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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.