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.

Server Claude Flow claude-flow
Category Destructive
Risk class Critical
Parameters 00 required

What wasm_gallery_remove_custom does on Claude Flow

AI agents call wasm_gallery_remove_custom to permanently remove resources in Claude Flow — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why wasm_gallery_remove_custom needs a policy

This tool permanently deletes a custom template from the WASM runtime registry. Deletion is irreversible and cannot be undone through normal means. The blast radius is high because removing a template could break dependent workflows, applications, or enterprise processes relying on that template.

From the tool's definition Tool name contains 'remove'; description states 'Remove a custom template from the WASM gallery by ID' and explicitly contrasts with filesystem deletion, indicating irreversible removal from a registry.

Questions about wasm_gallery_remove_custom

What does the wasm_gallery_remove_custom tool do? +

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 Claude Flow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on wasm_gallery_remove_custom? +

Register the Claude Flow 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 Claude Flow. Nothing to install.

What risk level is wasm_gallery_remove_custom? +

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.

Can I rate-limit wasm_gallery_remove_custom? +

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.

How do I block wasm_gallery_remove_custom completely? +

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.

What MCP server provides wasm_gallery_remove_custom? +

wasm_gallery_remove_custom is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.