comfy_agent_compute
One token's delivered compute from the points engine: compute_og (cumulative 0G delivered to compute for its pool, as the Infinity index records it), pool, ladder tier, and the basis sentence. The engine does not expose an agent router address, so router is null with a reason; nothing is invented...
This record as markdown: /tools/0g-axion-comfy-mcp/comfy-agent-compute.md
What comfy_agent_compute does on Comfy
AI agents call comfy_agent_compute 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 |
|---|---|---|---|
token | string | Yes | Token contract address (0x…, 40 hex chars). |
Parameters from the server's own tool schema.
Why comfy_agent_compute is rated Low
Even though comfy_agent_compute 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.
Risk signalsHandles credentials or secrets (token)
Attacks that exploit this kind of access
The rule that runs comfy_agent_compute 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_agent_compute, this is the rule to start with:
comfy_agent_compute is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Comfy, apply this rule, and every comfy_agent_compute call is checked against it from then on.
Questions about comfy_agent_compute
One token's delivered compute from the points engine: compute_og (cumulative 0G delivered to compute for its pool, as the Infinity index records it), pool, ladder tier, and the basis sentence. The engine does not expose an agent router address, so router is null with a reason; nothing is invented. A token the index does not know as launched is data:null; an index the engine could not read is live:false with outcome compute_unknown. It is categorised as a Read tool in the Comfy MCP Server, which means it retrieves data without modifying state.
comfy_agent_compute accepts 1 parameter: token. Required: token. The full parameter table on this page comes from the server's own tool schema.
Register the Comfy MCP server in PolicyLayer and add a rule for comfy_agent_compute: 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.
comfy_agent_compute 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 comfy_agent_compute 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 comfy_agent_compute. 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.
comfy_agent_compute 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.
More on Comfy, and thousands of servers like it.
This server
Across the catalogue