comfy_save_workflow

THE RISK

Medium Risk

Why comfy_save_workflow needs a policy

This tool creates and persists new workflow data in a local library with metadata, making it a Write operation. Severity is medium rather than high because the impact is limited to workflow definitions (not destructive, not financial, not arbitrary code execution). Confidence is high because the description is explicit and unambiguous about the save/creation action.

From the tool's definition Tool description explicitly states 'Save a workflow JSON to the MCP library', which creates or modifies data persistently. The metadata parameters (description, tags) further confirm intentional creation/organization of stored artifacts.

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

POLICY

How to control comfy_save_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_save_workflow:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "comfy_save_workflow": {
      "limits": [
        {
          "counter": "comfy_save_workflow_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

comfy_save_workflow stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

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.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More ComfyUI MCP Server tools

Destructive comfy_clear_queue Clear all pending items from the queue (does not affect currently running generation). Req 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_upload_image Upload an image to ComfyUI\ Read comfy_get_output_images List recent output images from ComfyUI\

All 14 ComfyUI MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about comfy_save_workflow

What does the comfy_save_workflow tool do? +

Save a workflow JSON to the MCP library for later reuse. Includes metadata like description and tags for organization. It is categorised as a Write tool in the ComfyUI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on comfy_save_workflow? +

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

comfy_save_workflow is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit comfy_save_workflow? +

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

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

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

CHECK YOUR STACK →