comfy_task

One task by id (tsk_ and 12 hex): the task, its acceptors in the board's order with their record counts (counts only, never a rate; comfy-funded and same-owner jobs counted apart), the buyer's standing counts, and the engine's now_s. Served verbatim. A task the board does not have is data:null.

SERVERComfy SOURCE@0g-axion/comfy-mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/0g-axion-comfy-mcp/comfy-task.md

WHAT IT DOES

What comfy_task does on Comfy

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

Parameter	Type	Required	Description
`id`	string	Yes	The task id, tsk_ and 12 lowercase hex characters.

Parameters from the server's own tool schema.

RISK

Why comfy_task is rated Low

Even though comfy_task only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs comfy_task safely

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

comfy_task Allowed

comfy_task 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": {
    "comfy_task": {}
  }
}

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

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

FAQ

Questions about comfy_task

What does the comfy_task tool do? +

What parameters does comfy_task accept? +

comfy_task accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on comfy_task? +

Register the Comfy MCP server in PolicyLayer and add a rule for comfy_task: 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 Comfy. Nothing to install.

What risk level is comfy_task? +

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

Can I rate-limit comfy_task? +

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

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

comfy_task is provided by the Comfy MCP server (@0g-axion/comfy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Comfy, and thousands of servers like it.

This server

All 9 Comfy tools →

Across the catalogue

The MCP Attack Database →

Guides

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