get_tvl
Get historical TVL data from DefiLlama
This record as markdown: /tools/indigoprotocol-indigo-mcp/get-tvl.md
What get_tvl does on Indigo Protocol MCP
AI agents call get_tvl to retrieve information from Indigo Protocol MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_tvl is rated Low
This tool retrieves historical financial metrics from DefiLlama, a read-only data aggregation service. It performs no writes, modifications, deletions, or financial transactions. The operation is informational only, presenting no risk of unintended data loss or state changes.
From the tool's definition Tool name 'get_tvl' and description 'Get historical TVL data from DefiLlama' indicate a data retrieval operation. TVL (Total Value Locked) is a metric queried from an external data source with no side effects.
Attacks that exploit this kind of access
The rule that runs get_tvl safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Indigo Protocol MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_tvl, this is the rule to start with:
get_tvl 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 Indigo Protocol MCP, apply this rule, and every get_tvl call is checked against it from then on.
Questions about get_tvl
Get historical TVL data from DefiLlama. It is categorised as a Read tool in the Indigo Protocol MCP MCP Server, which means it retrieves data without modifying state.
Register the Indigo Protocol MCP server in PolicyLayer and add a rule for get_tvl: 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 Indigo Protocol MCP. Nothing to install.
get_tvl 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_tvl 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_tvl. 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_tvl is provided by the Indigo Protocol MCP server (indigoprotocol/indigo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Indigo Protocol, and thousands of servers like it.
This server
Across the catalogue