wasm_gallery_config
Get the runtime configuration overrides applied to the active WASM gallery template. Use when native Read is wrong because gallery config overrides are stored in the WASM runtime state rather than as an editable config file.
This record as markdown: /tools/ruflo/wasm-gallery-config.md
What wasm_gallery_config does on Ruflo
AI agents call wasm_gallery_config 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.
Why wasm_gallery_config is rated Low
This tool retrieves and queries runtime configuration state from an active WASM gallery template. It performs no modifications, deletions, executions, or financial operations. The purpose is informational—to access configuration data that may not be available through standard read mechanisms.
From the tool's definition Tool description explicitly states 'Get the runtime configuration overrides' and 'Use when native Read is wrong because gallery config overrides are stored in the WASM runtime state'.
Attacks that exploit this kind of access
The rule that runs wasm_gallery_config 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_gallery_config, this is the rule to start with:
wasm_gallery_config is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every wasm_gallery_config call is checked against it from then on.
Questions about wasm_gallery_config
Get the runtime configuration overrides applied to the active WASM gallery template. Use when native Read is wrong because gallery config overrides are stored in the WASM runtime state rather than as an editable config file. 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_gallery_config: 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_gallery_config 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_gallery_config 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_gallery_config. 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_gallery_config 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.
More on Ruflo, and thousands of servers like it.
This server
Across the catalogue