# get_summary_dexs__by_protocol

Get summary of dex volume with historical data

Agent View of the PolicyLayer registry record for `get_summary_dexs__by_protocol`. HTML page: https://policylayer.com/tools/defillama/get-summary-dexs--by-protocol

## Facts

- Tool: `get_summary_dexs__by_protocol`
- Server: Defillama (`@nic0xflamel/defillama-mcp-server`) — https://policylayer.com/tools/defillama.md
- Install: `npx -y @nic0xflamel/defillama-mcp-server`
- Homepage: git+https://github.com/nic0flamel/notion-automation.git
- Risk category: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 3 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `protocol` | string | yes | protocol slug |
| `excludeTotalDataChart` | boolean | no | true to exclude aggregated chart from response |
| `excludeTotalDataChartBreakdown` | boolean | no | true to exclude broken down chart from response |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_summary_dexs__by_protocol",
    "arguments": {
      "protocol": "<protocol>"
    }
  }
}
```

## Why get_summary_dexs__by_protocol is rated Low

This is a data retrieval tool that queries DEX volume metrics and historical data from the DefiLlama API. It has no side effects, does not modify data, execute code, delete records, or move funds. The 'get_' prefix combined with the 'summary' and 'historical data' descriptors clearly indicate read-only query functionality.

From the tool's own definition: "Tool name contains 'get_' prefix and description states 'Get summary of dex volume with historical data' — purely retrieves/queries DEX volume information with no modification or execution capabilities."

## Use case

AI agents call get_summary_dexs__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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Defillama:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_summary_dexs__by_protocol": {}
  }
}
```

## Other tools on Defillama (13)

- `get_chart__by_pool` — Read — https://policylayer.com/tools/defillama/get-chart--by-pool.md
- `get_overview_dexs` — Read — https://policylayer.com/tools/defillama/get-overview-dexs.md
- `get_overview_dexs__by_chain` — Read — https://policylayer.com/tools/defillama/get-overview-dexs--by-chain.md
- `get_overview_fees` — Read — https://policylayer.com/tools/defillama/get-overview-fees.md
- `get_overview_fees__by_chain` — Read — https://policylayer.com/tools/defillama/get-overview-fees--by-chain.md
- `get_pools` — Read — https://policylayer.com/tools/defillama/get-pools.md
- `get_protocols` — Read — https://policylayer.com/tools/defillama/get-protocols.md
- `get_stablecoincharts_all` — Read — https://policylayer.com/tools/defillama/get-stablecoincharts-all.md
- `get_summary_fees__by_protocol` — Read — https://policylayer.com/tools/defillama/get-summary-fees--by-protocol.md
- `get_tvl__by_protocol` — Read — https://policylayer.com/tools/defillama/get-tvl--by-protocol.md
- `get_v2_chains` — Read — https://policylayer.com/tools/defillama/get-v2-chains.md
- `get_v2_historicalChainTvl` — Read — https://policylayer.com/tools/defillama/get-v2-historicalchaintvl.md
- `get_v2_historicalChainTvl__by_chain` — Read — https://policylayer.com/tools/defillama/get-v2-historicalchaintvl--by-chain.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=defillama · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/defillama