gt_wasm_parse_formula
Parse TOML formula content to AST using WASM (352x faster than JavaScript)
This record as markdown: /tools/io-github-ruvnet-claude-flow/gt-wasm-parse-formula.md
What gt_wasm_parse_formula does on Claude Flow
AI agents invoke gt_wasm_parse_formula 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_parse_formula is rated High
Parsing user-supplied formula content via WASM is an Execute operation: it processes and evaluates structured input whose effects depend on the content being parsed. While the tool itself appears to be a parser (which might seem like Read), WASM execution of arbitrary formulas with AST generation crosses into Execute territory, as malicious or uncontrolled formula content could trigger unintended operations.
From the tool's definition Tool uses WASM to parse and process arbitrary formula content into AST. WASM execution can trigger external operations and code evaluation depending on formula semantics.
Attacks that exploit this kind of access
The rule that runs gt_wasm_parse_formula safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gt_wasm_parse_formula, this is the rule to start with:
gt_wasm_parse_formula 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 Claude Flow, apply this rule, and every gt_wasm_parse_formula call is checked against it from then on.
Questions about gt_wasm_parse_formula
Parse TOML formula content to AST using WASM (352x faster than JavaScript). 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_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 Claude Flow. Nothing to install.
gt_wasm_parse_formula 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_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.
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.
gt_wasm_parse_formula 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.
Across the catalogue