get_chart__by_pool
Get historical APY and TVL of a pool
This record as markdown: /tools/defillama/get-chart--by-pool.md
What get_chart__by_pool does on Defillama
AI agents call get_chart__by_pool 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 |
|---|---|---|---|
pool | string | Yes | pool id, can be retrieved from /pools (property is called pool) |
Parameters from the server's own tool schema.
Why get_chart__by_pool is rated Low
This tool retrieves historical chart data (APY and TVL metrics) for a specific pool. It is a read-only query operation with no ability to modify, delete, or execute code. The blast radius of misuse is minimal—an agent could only retrieve information already publicly available through the DefiLlama API.
From the tool's definition Tool name contains 'get_chart' and description states 'Get historical APY and TVL of a pool' — both indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_chart__by_pool 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_chart__by_pool, this is the rule to start with:
get_chart__by_pool 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_chart__by_pool call is checked against it from then on.
Questions about get_chart__by_pool
Get historical APY and TVL of a pool. It is categorised as a Read tool in the Defillama MCP Server, which means it retrieves data without modifying state.
get_chart__by_pool accepts 1 parameter: pool. Required: pool. 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_chart__by_pool: 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_chart__by_pool 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_chart__by_pool 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_chart__by_pool. 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_chart__by_pool 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