get_overview_dexs
List all dexs along with summaries of their volumes and dataType history data
This record as markdown: /tools/defillama/get-overview-dexs.md
What get_overview_dexs does on Defillama
AI agents call get_overview_dexs 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 |
|---|---|---|---|
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 is rated Low
This tool retrieves and queries DEX protocol data (volumes, history) without modifying, executing operations, or causing side effects. It falls squarely into the Read category as a data retrieval endpoint. The low severity reflects that exposure of DeFi summary statistics poses minimal direct harm to the system or user assets.
From the tool's definition Tool name is 'get_overview_dexs' and description states 'List all dexs along with summaries of their volumes and dataType history data'. The word 'List' and 'summaries' indicate data retrieval with no modification or execution.
Attacks that exploit this kind of access
The rule that runs get_overview_dexs 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, this is the rule to start with:
get_overview_dexs 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 call is checked against it from then on.
Questions about get_overview_dexs
List all dexs along with summaries of their volumes and dataType history data. It is categorised as a Read tool in the Defillama MCP Server, which means it retrieves data without modifying state.
get_overview_dexs accepts 2 parameters: excludeTotalDataChart, excludeTotalDataChartBreakdown. 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: 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 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 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. 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 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