crypto.defi-protocol-history
Historical total-value-locked (TVL) time series for a DeFi protocol by slug (e.g. aave, lido, uniswap), via DefiLlama (free/keyless). Returns daily { date, tvlUsd } points (most recent N, default 90) plus the protocol\
This record as markdown: /tools/io-github-2s-io-mcp/crypto.defi-protocol-history.md
What crypto.defi-protocol-history does on Mcp
AI agents call crypto.defi-protocol-history to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why crypto.defi-protocol-history is rated Low
This tool queries and retrieves publicly available historical DeFi protocol data. It performs no writes, deletions, code execution, or financial operations. The data returned is informational only and useful for analysis or monitoring. Despite the crypto/DeFi context, no actual financial transactions or smart contract interactions occur—only read access to historical metrics.
From the tool's definition Tool returns historical time-series data (date, tvlUsd points) from DefiLlama with no modifications, deletions, or financial transactions. Description explicitly states it retrieves TVL data; the verb 'returns' confirms data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs crypto.defi-protocol-history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crypto.defi-protocol-history, this is the rule to start with:
crypto.defi-protocol-history 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 Mcp, apply this rule, and every crypto.defi-protocol-history call is checked against it from then on.
Questions about crypto.defi-protocol-history
Historical total-value-locked (TVL) time series for a DeFi protocol by slug (e.g. aave, lido, uniswap), via DefiLlama (free/keyless). Returns daily { date, tvlUsd } points (most recent N, default 90) plus the protocol\. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for crypto.defi-protocol-history: 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 Mcp. Nothing to install.
crypto.defi-protocol-history 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 crypto.defi-protocol-history 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 crypto.defi-protocol-history. 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.
crypto.defi-protocol-history is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue