# get_v2_historicalChainTvl__by_chain

Get historical TVL (excludes liquid staking and double counted tvl) of a chain

Agent View of the PolicyLayer registry record for `get_v2_historicalChainTvl__by_chain`. HTML page: https://policylayer.com/tools/defillama/get-v2-historicalchaintvl--by-chain

## Facts

- Tool: `get_v2_historicalChainTvl__by_chain`
- 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: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `chain` | string | yes | chain slug, you can get these from /chains or the chains property on /protocols |

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_v2_historicalChainTvl__by_chain",
    "arguments": {
      "chain": "<chain>"
    }
  }
}
```

## Why get_v2_historicalChainTvl__by_chain is rated Low

This tool queries and returns historical Total Value Locked (TVL) information for a blockchain chain. It performs a read-only operation that retrieves existing data without creating, modifying, executing code, deleting, or committing financial transactions. The lack of any side effects and the explicit 'get' pattern places it firmly in the Read category.

From the tool's own definition: "Tool name contains 'get_' prefix and description states it retrieves 'historical TVL' data. The verb 'Get' combined with action of querying historical blockchain metrics indicates data retrieval with no modification or execution capability."

## Use case

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

## 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_v2_historicalChainTvl__by_chain": {}
  }
}
```

## 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_dexs__by_protocol` — Read — https://policylayer.com/tools/defillama/get-summary-dexs--by-protocol.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

## 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
