get_exchange_reserves
chainpeek: Use when an agent must judge selling pressure or check reserves before depositing: a coin's exchange inflow or outflow. For DEX volume use get_dex_volume. Returns how much of a coin sits on centralised exchanges and whether it is flowing in or out: per exchange the amount, USD value, s...
This record as markdown: /tools/dev-tanod-tanod/get-exchange-reserves.md
What get_exchange_reserves does on Tanod
AI agents call get_exchange_reserves 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
days | integer | — | Length of the daily history of the total, in days (default 30, at most 90). |
asset | string | Yes | Token symbol held on exchanges, e.g. BTC, ETH, USDT, USDC (case-insensitive; matched exactly, so WBTC is not BTC). |
exchanges | object | — | Exchange slugs or names to include, e.g. binance-cex, okx, bybit, kucoin (default: every tracked exchange, at most 20 names). |
Parameters from the server's own tool schema.
Why get_exchange_reserves is rated Low
Even though get_exchange_reserves 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
Attacks that exploit this kind of access
The rule that runs get_exchange_reserves safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_exchange_reserves, this is the rule to start with:
get_exchange_reserves 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 Tanod, apply this rule, and every get_exchange_reserves call is checked against it from then on.
Questions about get_exchange_reserves
chainpeek: Use when an agent must judge selling pressure or check reserves before depositing: a coin's exchange inflow or outflow. For DEX volume use get_dex_volume. Returns how much of a coin sits on centralised exchanges and whether it is flowing in or out: per exchange the amount, USD value, share and the 1, 7 and 30-day change, totals and a daily history, from Tanod's cache of DefiLlama data. Cached DefiLlama data (refreshed every few hours), never live; the wallets are the exchanges' published or labelled wallets, so a rise means coins moved into them; symbols matched exactly; an unknown asset or exchange is a 422 and a missing or over-2-day-old cache a 503 (neither charged). Typically under 1 s (a local cache read). Price: USD 0.01. Free: 10 chain reads per IP per UTC day. Docs: https://tanod.dev/learn/exchange-reserves-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
get_exchange_reserves accepts 3 parameters: days, asset, exchanges. Required: asset. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for get_exchange_reserves: 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.
get_exchange_reserves 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 get_exchange_reserves 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 get_exchange_reserves. 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.
get_exchange_reserves 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.
This server
Across the catalogue