get_protocol_fees
chainpeek: Get protocol fees and revenue. For TVL use get_protocol_tvl. Returns a protocol's fees and revenue in USD over 24 hours, 7 days, 30 days, 1 year and all time, the change, the revenue-to-fees ratio and DefiLlama's definitions, from Tanod's cache of DefiLlama data. Cached DefiLlama data ...
This record as markdown: /tools/dev-tanod-tanod/get-protocol-fees.md
What get_protocol_fees does on Tanod
AI agents call get_protocol_fees 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 |
|---|---|---|---|
protocol | string | Yes | Protocol (or chain) name or slug, e.g. aave, uniswap, lido, ethereum (a parent such as aave sums its versions). An unknown name is a 422 with suggestions. |
Parameters from the server's own tool schema.
Why get_protocol_fees is rated Low
Even though get_protocol_fees 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_protocol_fees 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_protocol_fees, this is the rule to start with:
get_protocol_fees 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_protocol_fees call is checked against it from then on.
Questions about get_protocol_fees
chainpeek: Get protocol fees and revenue. For TVL use get_protocol_tvl. Returns a protocol's fees and revenue in USD over 24 hours, 7 days, 30 days, 1 year and all time, the change, the revenue-to-fees ratio and DefiLlama's definitions, from Tanod's cache of DefiLlama data. Cached DefiLlama data (refreshed every few hours), never live; as_of shows its age; revenue is DefiLlama's definition (see methodology); an unknown protocol 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.002. 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.
get_protocol_fees accepts 1 parameter: protocol. Required: protocol. 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_protocol_fees: 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_protocol_fees 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_protocol_fees 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_protocol_fees. 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_protocol_fees 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