AI agents call gt_wasm_match_pattern to retrieve information from Ruflo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data by matching patterns against a dataset and returning similar results. It performs no data creation, modification, deletion, code execution, or financial operations. The 'Find similar' language indicates a read-only retrieval operation. HNSW is a standard nearest-neighbor search algorithm used for information retrieval, not for data mutation or external command execution.
From the tool's definition Tool description states 'Find similar formulas or beads using HNSW pattern matching' — a search/query operation with no modification or side effects. The method is a vector similarity search using Hierarchical Navigable Small World (HNSW) indexing.
Attacks that exploit this kind of access
Find similar formulas or beads using HNSW pattern matching (150x-12500x faster). It is categorised as a Read tool in the Ruflo MCP Server, which means it retrieves data without modifying state.
Register the Ruflo MCP server in PolicyLayer and add a rule for gt_wasm_match_pattern: 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_wasm_match_pattern is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gt_wasm_match_pattern 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_match_pattern. 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_match_pattern 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.
gt_wasm_match_pattern 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 →