Get the current ComfyUI queue status.
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 only retrieves information about the current state of the ComfyUI processing queue. It has no side effects, does not create, modify, delete, or execute any operations. It is a simple status query that returns data about the system state without altering it. Severity is low because even if misused, reading queue status cannot cause harm to the system or data.
From the tool's definition Tool retrieves queue status information with no parameters that modify state. Description explicitly states 'Get the current ComfyUI queue status' — a pure read operation that queries existing data.
Attacks that exploit this kind of access
Get the current ComfyUI queue status. 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 (m2ai-archive/comfyui-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →