wasm_gallery_remove_custom
Remove a custom template from the WASM gallery by ID. Use when native Bash rm is wrong because custom templates exist only inside the WASM runtime registry and cannot be deleted via filesystem operations.
This record as markdown: /tools/ruflo/wasm-gallery-remove-custom.md
What wasm_gallery_remove_custom does on Ruflo
AI agents call wasm_gallery_remove_custom to permanently remove resources in Ruflo, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why wasm_gallery_remove_custom is rated Critical
This tool irreversibly deletes data (a custom WASM template) from a registry. Deletion cannot be undone, and removal of templates could break dependent workflows, configurations, or agent deployments in the Ruflo multi-agent orchestration system. The tool is called 'remove_custom' and explicitly performs deletion ('Remove...from the WASM gallery').
From the tool's definition Remove a custom template from the WASM gallery by ID. Use when native Bash rm is wrong because custom templates exist only inside the WASM runtime registry and cannot be deleted via filesystem operations.
Attacks that exploit this kind of access
The rule that runs wasm_gallery_remove_custom 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_remove_custom, this is the rule to start with:
wasm_gallery_remove_custom is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every wasm_gallery_remove_custom call is checked against it from then on.
Questions about wasm_gallery_remove_custom
Remove a custom template from the WASM gallery by ID. Use when native Bash rm is wrong because custom templates exist only inside the WASM runtime registry and cannot be deleted via filesystem operations. It is categorised as a Destructive tool in the Ruflo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ruflo MCP server in PolicyLayer and add a rule for wasm_gallery_remove_custom: 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_remove_custom is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the wasm_gallery_remove_custom 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_remove_custom. 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_remove_custom 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.
Across the catalogue