get_summary_fees__by_protocol
Get summary of protocol fees and revenue with historical data
This record as markdown: /tools/defillama/get-summary-fees--by-protocol.md
What get_summary_fees__by_protocol does on Defillama
AI agents call get_summary_fees__by_protocol to retrieve information from Defillama 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 |
|---|---|---|---|
dataType | string | — | Desired data type, dailyFees by default. |
protocol | string | Yes | protocol slug |
Parameters from the server's own tool schema.
Why get_summary_fees__by_protocol is rated Low
This tool retrieves and aggregates historical financial summary data (fees and revenue) for DeFi protocols. It performs a read-only query operation with no side effects, data modification, or irreversible actions.
From the tool's definition Tool name 'get_summary_fees__by_protocol' and description 'Get summary of protocol fees and revenue with historical data' indicate a retrieval operation that queries existing data without modification, deletion, or execution of arbitrary operations.
Attacks that exploit this kind of access
The rule that runs get_summary_fees__by_protocol safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Defillama, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_summary_fees__by_protocol, this is the rule to start with:
get_summary_fees__by_protocol 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 Defillama, apply this rule, and every get_summary_fees__by_protocol call is checked against it from then on.
Questions about get_summary_fees__by_protocol
Get summary of protocol fees and revenue with historical data. It is categorised as a Read tool in the Defillama MCP Server, which means it retrieves data without modifying state.
get_summary_fees__by_protocol accepts 2 parameters: dataType, protocol. Required: protocol. The full parameter table on this page comes from the server's own tool schema.
Register the Defillama MCP server in PolicyLayer and add a rule for get_summary_fees__by_protocol: 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 Defillama. Nothing to install.
get_summary_fees__by_protocol 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_summary_fees__by_protocol 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_summary_fees__by_protocol. 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_summary_fees__by_protocol is provided by the Defillama MCP server (@nic0xflamel/defillama-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Defillama, and thousands of servers like it.
This server
Across the catalogue