comfy_tokens
List the newest launched tokens on comfy.fun (0G mainnet) with market fields in 0G: price, 24h change (percent) and volume, FDV, market cap, liquidity, holders, traders. A token that has never traded reports null market figures: unknown is not zero. The list leaves out what the site's lists leave...
This record as markdown: /tools/0g-axion-comfy-mcp/comfy-tokens.md
What comfy_tokens does on Comfy
AI agents call comfy_tokens 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 |
|---|---|---|---|
limit | integer | — | How many tokens, newest launch first. |
Parameters from the server's own tool schema.
Why comfy_tokens is rated Low
Even though comfy_tokens 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
The rule that runs comfy_tokens 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_tokens, this is the rule to start with:
comfy_tokens 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_tokens call is checked against it from then on.
Questions about comfy_tokens
List the newest launched tokens on comfy.fun (0G mainnet) with market fields in 0G: price, 24h change (percent) and volume, FDV, market cap, liquidity, holders, traders. A token that has never traded reports null market figures: unknown is not zero. The list leaves out what the site's lists leave out (test launches, reserved tickers, opening-fee pools) and says how many in hidden; comfy_token still reads them by address. It is categorised as a Read tool in the Comfy MCP Server, which means it retrieves data without modifying state.
comfy_tokens accepts 1 parameter: limit. 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_tokens: 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_tokens 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_tokens 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_tokens. 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_tokens 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