comfy_clear_queue

THE RISK

Critical Risk

Why comfy_clear_queue needs a policy

This tool permanently deletes queued workflow items, which cannot be undone. Although it does not affect currently running generations, it destroys pending work items. This qualifies as Destructive rather than Write (which is reversible). The medium severity reflects that the blast radius is limited to the local queue—no external systems or financial impact—but the loss of queued work could disrupt user workflows.

From the tool's definition Tool description states 'Clear all pending items from the queue' — this irreversibly removes queued generation jobs without the ability to recover them.

Risk signalsBulk/mass operation — affects multiple targets

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

POLICY

How to control comfy_clear_queue

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_clear_queue:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "comfy_clear_queue"
  ]
}

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

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

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More ComfyUI MCP Server tools

Destructive comfy_delete_workflow Delete a saved workflow from the MCP library. Requires confirmation for safety. Execute comfy_cancel_generation Cancel a specific generation or interrupt the currently executing generation. Can optional Execute comfy_wait_for_completion Block until a generation completes or fails. Returns final outputs with image paths. Usefu Execute comfy_generate_simple Quick image generation using pre-configured workflow templates (flux_txt2img, sd15_txt2img Execute comfy_submit_workflow Submit a complete workflow JSON to ComfyUI for execution. Supports parameter overrides for Write comfy_save_workflow Save a workflow JSON to the MCP library for later reuse. Includes metadata like descriptio Write comfy_upload_image Upload an image to ComfyUI\ Read comfy_get_output_images List recent output images from ComfyUI\

All 14 ComfyUI MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in ComfyUI MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about comfy_clear_queue

What does the comfy_clear_queue tool do? +

Clear all pending items from the queue (does not affect currently running generation). Requires confirmation. 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_clear_queue? +

Register the ComfyUI MCP Server MCP server in PolicyLayer and add a rule for comfy_clear_queue: 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_clear_queue? +

comfy_clear_queue 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_clear_queue? +

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

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

comfy_clear_queue 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.

CHECK YOUR STACK →