comfy_trades
Recent trades for one token, newest first: side, trader, token amount, 0G volume, execution price and spot price in 0G, tx hash. A side the index did not state stays null; data:null means the index does not know the token.
This record as markdown: /tools/0g-axion-comfy-mcp/comfy-trades.md
What comfy_trades does on Comfy
AI agents call comfy_trades 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 trades, newest first. |
token | string | Yes | Token contract address (0x…, 40 hex chars). |
Parameters from the server's own tool schema.
Why comfy_trades is rated Low
Even though comfy_trades 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_trades 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_trades, this is the rule to start with:
comfy_trades 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_trades call is checked against it from then on.
Questions about comfy_trades
Recent trades for one token, newest first: side, trader, token amount, 0G volume, execution price and spot price in 0G, tx hash. A side the index did not state stays null; data:null means the index does not know the token. It is categorised as a Read tool in the Comfy MCP Server, which means it retrieves data without modifying state.
comfy_trades accepts 2 parameters: limit, 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_trades: 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_trades 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_trades 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_trades. 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_trades 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