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

Agent View of the PolicyLayer registry record for `comfy_tokens`. HTML page: https://policylayer.com/tools/0g-axion-comfy-mcp/comfy-tokens

## Facts

- Tool: `comfy_tokens`
- Server: Comfy (`@0g-axion/comfy-mcp`) — https://policylayer.com/tools/0g-axion-comfy-mcp.md
- Install: `npx -y @0g-axion/comfy-mcp`
- Homepage: https://www.npmjs.com/package/@0g-axion/comfy-mcp
- Risk category: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 1
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `limit` | integer | no | How many tokens, newest launch first. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "comfy_tokens",
    "arguments": {}
  }
}
```

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

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Comfy:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "comfy_tokens": {}
  }
}
```

## Other tools on Comfy (8)

- `comfy_agent_compute` — Read — https://policylayer.com/tools/0g-axion-comfy-mcp/comfy-agent-compute.md
- `comfy_bazaar` — Read — https://policylayer.com/tools/0g-axion-comfy-mcp/comfy-bazaar.md
- `comfy_compute_funded` — Read — https://policylayer.com/tools/0g-axion-comfy-mcp/comfy-compute-funded.md
- `comfy_jobs` — Read — https://policylayer.com/tools/0g-axion-comfy-mcp/comfy-jobs.md
- `comfy_task` — Read — https://policylayer.com/tools/0g-axion-comfy-mcp/comfy-task.md
- `comfy_tasks` — Read — https://policylayer.com/tools/0g-axion-comfy-mcp/comfy-tasks.md
- `comfy_token` — Read — https://policylayer.com/tools/0g-axion-comfy-mcp/comfy-token.md
- `comfy_trades` — Read — https://policylayer.com/tools/0g-axion-comfy-mcp/comfy-trades.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=0g-axion-comfy-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0g-axion-comfy-mcp