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

get_dex_price_candles

chainpeek: Get ETH or BTC OHLCV price candles from on-chain DEX swaps. For the oracle price now use get_token_price. Returns OHLCV candles for ETH (WETH/USDC) or BTC (cbBTC/USDC) in USDC from public Uniswap v3 swaps on Base, at 5m, 15m, 1h, 4h or 1d, with the pool, fee tier and the block the data...

SERVERTanod SOURCEhttps://tanod.dev/mcp
Low RISK CLASS
Category Read
Parameters 31 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-price-candles.md

What get_dex_price_candles does on Tanod

AI agents call get_dex_price_candles 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
pair string Yes WETH/USDC (ETH in USDC, Uniswap v3 0.3% pool on Base) or cbBTC/USDC (BTC in USDC, Uniswap v3 0.05% pool on Base).
limit object — Number of candles, newest last. Default 48 (1d: 30). Lookback caps: 5m and 15m 200, 1h 168, 4h 42, 1d 30.
interval string — Candle length, UTC-aligned.

Parameters from the server's own tool schema.

Why get_dex_price_candles is rated Low

Even though get_dex_price_candles 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.

Questions about get_dex_price_candles

What does the get_dex_price_candles tool do? +

chainpeek: Get ETH or BTC OHLCV price candles from on-chain DEX swaps. For the oracle price now use get_token_price. Returns OHLCV candles for ETH (WETH/USDC) or BTC (cbBTC/USDC) in USDC from public Uniswap v3 swaps on Base, at 5m, 15m, 1h, 4h or 1d, with the pool, fee tier and the block the data is current to (about a minute behind). Computed by Tanod from one allow-listed pool per pair, not an exchange feed: DEX prices can differ from centralized exchanges; a candle without swaps repeats the previous close; the last candle is still forming. Informational only, not investment advice. A bad pair, interval or limit is a 422 before any payment; a 503 warming_up (index still loading) or rpc_unavailable is not charged. Typically under 0.1 s (served from an index kept current in the background). Price: USD 0.003. Free: 10 chain reads per IP per UTC day. Docs: https://tanod.dev/learn/crypto-ohlcv-candles-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_price_candles accept? +

get_dex_price_candles accepts 3 parameters: pair, limit, interval. Required: pair. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_dex_price_candles? +

Register the Tanod MCP server in PolicyLayer and add a rule for get_dex_price_candles: 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_price_candles? +

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

Can I rate-limit get_dex_price_candles? +

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

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

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