Get the current ComfyUI queue status. Returns information about queued and running jobs, including: - Currently running prompts - Queued prompts waiting to execute - Queue position and estimated wait times This tool provides async awareness - the AI can check if a job is still running or queued b...
AI agents call get_queue_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 queries the state of an asynchronous job queue and returns metadata about running and pending prompts. It has no side effects—it neither creates, modifies, deletes jobs nor executes arbitrary code. The AI uses it for status awareness before deciding on further actions.
From the tool's definition Tool description states it 'Get[s] the current ComfyUI queue status' and 'Returns information about queued and running jobs'. The verb 'Get' and the return-only nature (no parameters that modify state) indicate a read-only retrieval operation.
Documented attack patterns abuse exactly the kind of access get_queue_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 get_queue_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_queue_status": {}
}
}get_queue_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 ComfyUI queue status. Returns information about queued and running jobs, including: - Currently running prompts - Queued prompts waiting to execute - Queue position and estimated wait times This tool provides async awareness - the AI can check if a job is still running or queued before polling for completion. Returns: Dict with 'queue_running' and 'queue_pending' lists, each containing prompt IDs and associated metadata. 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 get_queue_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.
get_queue_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 get_queue_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 get_queue_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.
get_queue_status is provided by the ComfyUI MCP Server MCP server (joenorton/comfyui-mcp-server). 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.
15 ComfyUI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.