comfyui.get_job_status

Get queue/status for a submitted prompt

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/comfyui.get-job-status.md

WHAT IT DOES

What comfyui.get_job_status does on CoWork OS

AI agents call comfyui.get_job_status to retrieve information from CoWork OS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why comfyui.get_job_status is rated Low

This tool retrieves the current status of a queued job in ComfyUI (a generative AI image processing system). It performs a simple status lookup with no side effects—no data is created, modified, deleted, or executed. The operation is informational only, making it a Read category tool with low risk if misused by an AI agent.

From the tool's definition Tool name and description indicate querying operational status: 'Get queue/status for a submitted prompt'. The verb 'get' and noun 'status' are characteristic of read operations that retrieve information without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs comfyui.get_job_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For comfyui.get_job_status, this is the rule to start with:

comfyui.get_job_status Allowed

comfyui.get_job_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "comfyui.get_job_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every comfyui.get_job_status call is checked against it from then on.

FAQ

Questions about comfyui.get_job_status

What does the comfyui.get_job_status tool do? +

Get queue/status for a submitted prompt. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on comfyui.get_job_status? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for comfyui.get_job_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 CoWork OS. Nothing to install.

What risk level is comfyui.get_job_status? +

comfyui.get_job_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit comfyui.get_job_status? +

Yes. Add a rate_limit block to the comfyui.get_job_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.

How do I block comfyui.get_job_status completely? +

Set action: deny in the PolicyLayer policy for comfyui.get_job_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.

What MCP server provides comfyui.get_job_status? +

comfyui.get_job_status is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →