Get historical APY and TVL data for a yield pool.
AI agents call getYieldHistory to retrieve information from Boosty MCP DeFi Platform without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical financial data (APY and TVL) without creating side effects, modifying state, executing code, or moving funds. It is a pure read operation on yield pool data. Despite the DeFi context of the server, this specific tool performs no destructive, financial, or executable actions—it only fetches and returns information.
From the tool's definition Tool name 'getYieldHistory' and description 'Get historical APY and TVL data for a yield pool' indicate data retrieval only. No state modification, deletion, or execution of operations occurs—it queries and returns historical yield metrics.
Documented attack patterns abuse exactly the kind of access getYieldHistory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Boosty MCP DeFi Platform, and nothing reaches the server without passing your rules. This is the rule we recommend for getYieldHistory:
{
"version": "1",
"default": "deny",
"tools": {
"getYieldHistory": {}
}
}getYieldHistory is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get historical APY and TVL data for a yield pool. It is categorised as a Read tool in the Boosty MCP DeFi Platform MCP Server, which means it retrieves data without modifying state.
Register the Boosty MCP DeFi Platform MCP server in PolicyLayer and add a rule for getYieldHistory: 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 Boosty MCP DeFi Platform. Nothing to install.
getYieldHistory 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 getYieldHistory 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 getYieldHistory. 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.
getYieldHistory is provided by the Boosty MCP DeFi Platform MCP server (nirholas/boosty). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Boosty MCP DeFi Platform, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
80 Boosty MCP DeFi Platform tools catalogued and risk-classified — across an index of 43,000+ MCP servers.