Critical Risk →

comfy_delete_workflow

Delete a saved workflow from the MCP library. Requires confirmation for safety.

How to control comfy_delete_workflow ↓

What comfy_delete_workflow does on ComfyUI MCP Server

AI agents call comfy_delete_workflow to permanently remove resources in ComfyUI MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why comfy_delete_workflow needs a policy

This tool irreversibly deletes saved workflows, removing data that cannot be recovered without external backups. While the description notes a confirmation requirement mitigates risk somewhat, the core operation is destructive deletion.

From the tool's definition Delete a saved workflow from the MCP library. Requires confirmation for safety.

Documented attack patterns abuse exactly the kind of access comfy_delete_workflow gives an agent:

How to control comfy_delete_workflow

PolicyLayer is an MCP gateway — it sits between your AI agents and ComfyUI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for comfy_delete_workflow:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "comfy_delete_workflow"
  ]
}

comfy_delete_workflow disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register ComfyUI MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about comfy_delete_workflow

What does the comfy_delete_workflow tool do? +

Delete a saved workflow from the MCP library. Requires confirmation for safety. It is categorised as a Destructive tool in the ComfyUI MCP Server 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 comfy_delete_workflow? +

Register the ComfyUI MCP Server MCP server in PolicyLayer and add a rule for comfy_delete_workflow: 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 ComfyUI MCP Server. Nothing to install.

What risk level is comfy_delete_workflow? +

comfy_delete_workflow 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 comfy_delete_workflow? +

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

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

comfy_delete_workflow is provided by the ComfyUI MCP Server MCP server (nikolaibibo/claude-comfyui-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ComfyUI MCP Server tool call.

Start from ComfyUI MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

14 ComfyUI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.