AI agents call wasm_agent_files 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 information about WebAssembly agents without side effects. It performs a query/fetch operation typical of Read category tools. The description is brief but the 'Get' verb clearly indicates data retrieval. Low severity because unauthorized access to agent file metadata has limited blast radius compared to agent execution or termination capabilities visible in sibling tools.
From the tool's definition Tool name 'wasm_agent_files' and description 'Get a WASM agent' indicate a retrieval operation. The verb 'Get' is a read operation that queries or retrieves data about WASM agents without modifying state.
Attacks that exploit this kind of access
Get a WASM agent\. 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 wasm_agent_files: 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.
wasm_agent_files 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 wasm_agent_files 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 wasm_agent_files. 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.
wasm_agent_files 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.
wasm_agent_files 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 →