comfyui.submit_workflow
Submit a ComfyUI workflow JSON graph
This record as markdown: /tools/cowork-os/comfyui.submit-workflow.md
What comfyui.submit_workflow does on CoWork OS
AI agents invoke comfyui.submit_workflow to trigger actions in CoWork OS. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why comfyui.submit_workflow is rated High
Submitting a workflow graph to ComfyUI triggers execution of an arbitrary image/video generation pipeline on the local system. The effect depends entirely on the workflow JSON provided, which can invoke arbitrary ComfyUI nodes including those that write files, call external APIs, or run custom scripts.
From the tool's definition Submit a ComfyUI workflow JSON graph
Attacks that exploit this kind of access
The rule that runs comfyui.submit_workflow safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For comfyui.submit_workflow, this is the rule to start with:
comfyui.submit_workflow stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every comfyui.submit_workflow call is checked against it from then on.
Questions about comfyui.submit_workflow
Submit a ComfyUI workflow JSON graph. It is categorised as a Execute tool in the CoWork OS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the CoWork OS MCP server in PolicyLayer and add a rule for comfyui.submit_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 CoWork OS. Nothing to install.
comfyui.submit_workflow is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the comfyui.submit_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.
Set action: deny in the PolicyLayer policy for comfyui.submit_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.
comfyui.submit_workflow is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
Across the catalogue