Get the current status and progress of a specific generation or the overall queue. Returns queue position, progress, and output paths when available.
AI agents call comfy_get_status to retrieve information from ComfyUI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about image generation processes and queue state without modifying any data, triggering actions, or causing irreversible changes. It is a read-only operation analogous to a status check or monitoring query. The blast radius of misuse is minimal since an agent cannot cause harm by querying status information.
From the tool's definition Tool description states it 'Get[s] the current status and progress' and 'Returns queue position, progress, and output paths' — purely informational queries with no side effects.
Documented attack patterns abuse exactly the kind of access comfy_get_status gives an agent:
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_get_status:
{
"version": "1",
"default": "deny",
"tools": {
"comfy_get_status": {}
}
}comfy_get_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the current status and progress of a specific generation or the overall queue. Returns queue position, progress, and output paths when available. It is categorised as a Read tool in the ComfyUI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ComfyUI MCP Server MCP server in PolicyLayer and add a rule for comfy_get_status: 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.
comfy_get_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the comfy_get_status 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_get_status. 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_get_status 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.
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.
Free to start. No card required.
14 ComfyUI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.