comfy_restart
Restart ComfyUI and wait until its local HTTP API responds.
This record as markdown: /tools/mcp-control-plane/comfy-restart.md
What comfy_restart does on Mcp Control Plane
AI agents invoke comfy_restart 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_restart is rated High
This tool triggers a restart of ComfyUI, an external service. Restarts are Execute-category actions because they run a command/operation whose effects depend on the system state. While reversible (unlike Destructive), the restart operation itself is a control action that interrupts service availability and may cause in-flight operations to fail.
From the tool's definition Tool name 'comfy_restart' and description 'Restart ComfyUI and wait until its local HTTP API responds' indicate execution of a service restart operation with external effects.
Attacks that exploit this kind of access
The rule that runs comfy_restart 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_restart, this is the rule to start with:
comfy_restart 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_restart call is checked against it from then on.
Questions about comfy_restart
Restart ComfyUI and wait until its local HTTP API responds. 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_restart: 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_restart 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_restart 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_restart. 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_restart 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