get_overview_dexs__by_chain
List all dexs along with summaries of their volumes and dataType history data filtering by chain
This record as markdown: /tools/defillama/get-overview-dexs--by-chain.md
What get_overview_dexs__by_chain does on Defillama
AI agents call get_overview_dexs__by_chain 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 |
|---|---|---|---|
chain | string | Yes | chain name, list of all supported chains can be found under allChains attribute in /overview/dexs response |
excludeTotalDataChart | boolean | — | true to exclude aggregated chart from response |
excludeTotalDataChartBreakdown | boolean | — | true to exclude broken down chart from response |
Parameters from the server's own tool schema.
Why get_overview_dexs__by_chain is rated Low
This tool retrieves DEX overview information filtered by chain. It is a read-only data query operation that returns existing data from the DefiLlama API with no capability to modify, execute code, delete data, or move funds. The blast radius of misuse is minimal — an agent could only retrieve more data than intended, which poses low risk.
From the tool's definition Tool name contains 'get_overview' and description states 'List all dexs along with summaries' — purely retrieves and queries data without modification or side effects. No mentions of write, execute, or delete operations.
Attacks that exploit this kind of access
The rule that runs get_overview_dexs__by_chain 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_overview_dexs__by_chain, this is the rule to start with:
get_overview_dexs__by_chain 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_overview_dexs__by_chain call is checked against it from then on.
Questions about get_overview_dexs__by_chain
List all dexs along with summaries of their volumes and dataType history data filtering by chain. It is categorised as a Read tool in the Defillama MCP Server, which means it retrieves data without modifying state.
get_overview_dexs__by_chain accepts 3 parameters: chain, excludeTotalDataChart, excludeTotalDataChartBreakdown. Required: chain. 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_overview_dexs__by_chain: 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_overview_dexs__by_chain 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_overview_dexs__by_chain 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_overview_dexs__by_chain. 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_overview_dexs__by_chain 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