comfy_interrupt
Interrupt the current ComfyUI generation.
This record as markdown: /tools/mcp-control-plane/comfy-interrupt.md
What comfy_interrupt does on Mcp Control Plane
AI agents invoke comfy_interrupt to trigger actions in Mcp Control Plane. 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 comfy_interrupt is rated High
This tool actively stops/interrupts an ongoing process (ComfyUI image generation). It's an external operation that triggers an action on a running process. While it doesn't delete data, it terminates an in-progress execution, making it an Execute-category action. Severity is medium because interrupting a generation job can cause loss of in-progress work but has limited broader blast radius.
From the tool's definition Interrupt the current ComfyUI generation
Attacks that exploit this kind of access
The rule that runs comfy_interrupt safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For comfy_interrupt, this is the rule to start with:
comfy_interrupt 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 Mcp Control Plane, apply this rule, and every comfy_interrupt call is checked against it from then on.
Questions about comfy_interrupt
Interrupt the current ComfyUI generation. It is categorised as a Execute tool in the Mcp Control Plane MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for comfy_interrupt: 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 Mcp Control Plane. Nothing to install.
comfy_interrupt 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 comfy_interrupt 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 comfy_interrupt. 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.
comfy_interrupt is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
Across the catalogue