Low Risk

get_job

get_job

How to control get_job ↓

What get_job does on ComfyUI MCP Server

AI agents call get_job 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.

Low Risk

Why get_job needs a policy

Based on naming convention and server context, 'get_job' appears to retrieve status or details about a generation job without side effects. No destructive, financial, or execution capabilities are implied. Confidence is moderately high despite empty description because the verb 'get' and surrounding tool patterns strongly suggest a read-only operation.

From the tool's definition Tool name 'get_job' suggests retrieval of job information with no modification capability. Description is empty, but context from sibling tools (cancel_job, get_queue_status, get_asset_metadata) indicates this is part of a query/monitoring API.

Documented attack patterns abuse exactly the kind of access get_job gives an agent:

How to control get_job

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_job:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_job": {}
  }
}

get_job is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register ComfyUI MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_job

What does the get_job tool do? +

get_job. It is categorised as a Read tool in the ComfyUI MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_job? +

Register the ComfyUI MCP Server MCP server in PolicyLayer and add a rule for get_job: 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.

What risk level is get_job? +

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

Can I rate-limit get_job? +

Yes. Add a rate_limit block to the get_job 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 get_job completely? +

Set action: deny in the PolicyLayer policy for get_job. 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 get_job? +

get_job 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.

Enforce policy on every ComfyUI MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.