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

get_protocol_tvl

chainpeek: Get protocol or chain TVL with 1d and 7d change. For fees and revenue use get_protocol_fees; for DEX volume use get_dex_volume. Returns the TVL of a protocol or chain with 1d and 7d change, the protocol's chains or the chain's largest protocols, or the largest chains and protocols, fro...

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-protocol-tvl.md

What get_protocol_tvl does on Tanod

AI agents call get_protocol_tvl 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, e.g. Ethereum, Base, Solana, BSC, Arbitrum (common aliases such as bnb and eth work). With protocol: that protocol's TVL on the chain. Alone: the ch
limit integer — Rows in a ranking or a breakdown, 1-50 (default 10).
protocol object — Protocol name or slug, e.g. aave, uniswap-v3, lido (a parent such as aave sums its versions). Omit for a chain or the overview. An unknown name is a 422 with su

Parameters from the server's own tool schema.

Why get_protocol_tvl is rated Low

Even though get_protocol_tvl 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_protocol_tvl

What does the get_protocol_tvl tool do? +

chainpeek: Get protocol or chain TVL with 1d and 7d change. For fees and revenue use get_protocol_fees; for DEX volume use get_dex_volume. Returns the TVL of a protocol or chain with 1d and 7d change, the protocol's chains or the chain's largest protocols, or the largest chains and protocols, 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; 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_protocol_tvl accept? +

get_protocol_tvl 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_protocol_tvl? +

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

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

Can I rate-limit get_protocol_tvl? +

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

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

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