wasm_gallery_export
Export all custom WASM gallery templates as a JSON snapshot. Use when native Read/cat is wrong because custom templates live inside the WASM runtime store and are not persisted as individual files on disk.
This record as markdown: /tools/ruflo/wasm-gallery-export.md
What wasm_gallery_export does on Ruflo
AI agents call wasm_gallery_export 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_export is rated Low
The tool reads/exports data (WASM gallery templates) as a JSON snapshot. It retrieves data from the WASM runtime store without modifying, deleting, or executing anything. The word 'export' here means read/dump, not a destructive operation. Severity is low since it only exposes template configuration data.
From the tool's definition Export all custom WASM gallery templates as a JSON snapshot... not persisted as individual files on disk
Attacks that exploit this kind of access
The rule that runs wasm_gallery_export 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_export, this is the rule to start with:
wasm_gallery_export 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_export call is checked against it from then on.
Questions about wasm_gallery_export
Export all custom WASM gallery templates as a JSON snapshot. Use when native Read/cat is wrong because custom templates live inside the WASM runtime store and are not persisted as individual files on disk. 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_export: 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_export 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_export 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_export. 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_export 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