New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_dex_volume

chainpeek: Get DEX volume by protocol and chain. For TVL use get_protocol_tvl. Returns DEX volume over 24 hours, 7 days and 30 days with change: a DEX's chains, a chain's largest DEXs, a DEX on a chain, or the market total and the largest DEXs, from Tanod's cache of DefiLlama data. Input: optiona...

SERVERTanod SOURCEhttps://tanod.dev/mcp
Low RISK CLASS
Category Read
Parameters 30 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-tanod-tanod/get-dex-volume.md

What get_dex_volume does on Tanod

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

ParameterTypeRequiredDescription
chain object — Chain name among the 25 chains with the most DEX volume, e.g. Solana, Ethereum, Base, BSC. With protocol: that DEX's volume on the chain. Alone: the chain and i
limit integer — Rows in a ranking or a breakdown, 1-50 (default 10).
protocol object — DEX name or slug, e.g. uniswap, uniswap-v3, curve-dex, pancakeswap-amm (a parent such as uniswap sums its versions). Omit for a chain or the overview.

Parameters from the server's own tool schema.

Why get_dex_volume is rated Low

Even though get_dex_volume 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 signalsBulk/mass operation — affects multiple targets

Questions about get_dex_volume

What does the get_dex_volume tool do? +

chainpeek: Get DEX volume by protocol and chain. For TVL use get_protocol_tvl. Returns DEX volume over 24 hours, 7 days and 30 days with change: a DEX's chains, a chain's largest DEXs, a DEX on a chain, or the market total and the largest DEXs, from Tanod's cache of DefiLlama data. Input: optional protocol, optional chain and limit; give one, both or neither. Cached DefiLlama data (refreshed every few hours), never live; as_of shows its age; chain tables cover the 25 chains with the most volume; an unknown name is a 422 with suggestions and a missing or over-2-day-old cache a 503 (neither charged). Informational only. Typically under 1 s (a local cache read). Price: USD 0.004. Free: 10 chain reads per IP per UTC day. Docs: https://tanod.dev/learn/defi-data-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.

What parameters does get_dex_volume accept? +

get_dex_volume accepts 3 parameters: chain, limit, protocol. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_dex_volume? +

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

What risk level is get_dex_volume? +

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

Can I rate-limit get_dex_volume? +

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

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

get_dex_volume is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Tanod, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Tanod's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.