wasm_agent_tools

List the tools registered on a WASM agent sandbox. Use when native Task is wrong because the tool registry lives inside the WASM runtime and cannot be inspected from the host via standard reflection.

SERVERRuflo SOURCEruvnet/ruflo

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ruflo/wasm-agent-tools.md

WHAT IT DOES

What wasm_agent_tools does on Ruflo

AI agents call wasm_agent_tools to retrieve information from Ruflo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why wasm_agent_tools is rated Low

This tool queries and retrieves information about registered tools within a WASM sandbox runtime. It performs a read-only inspection operation with no side effects, data modification, code execution, or destructive actions. The primary purpose is introspection of the sandbox state. While it reveals internal tool capabilities, this is informational only and poses minimal risk if misused by an AI agent.

From the tool's definition Tool name contains 'List' behavior (list tools); description states 'List the tools registered on a WASM agent sandbox' and explicitly indicates inspection/querying of a runtime registry with no modification or execution rights.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wasm_agent_tools 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 wasm_agent_tools, this is the rule to start with:

wasm_agent_tools Allowed

wasm_agent_tools is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wasm_agent_tools": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every wasm_agent_tools call is checked against it from then on.

FAQ

Questions about wasm_agent_tools

What does the wasm_agent_tools tool do? +

List the tools registered on a WASM agent sandbox. Use when native Task is wrong because the tool registry lives inside the WASM runtime and cannot be inspected from the host via standard reflection. It is categorised as a Read tool in the Ruflo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on wasm_agent_tools? +

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

wasm_agent_tools is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit wasm_agent_tools? +

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

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

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

KEEP EXPLORING

More on Ruflo, and thousands of servers like it.

This server

All 496 Ruflo tools →

Across the catalogue

get_agent on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →