compareYieldHistoryTool
Compares historical yield performance across multiple pools, analyzing metrics like APY, volatility, and TVL trends
This record as markdown: /tools/nanidao-agentek/compareyieldhistorytool.md
What compareYieldHistoryTool does on Agentek Eth
AI agents call compareYieldHistoryTool to retrieve information from Agentek Eth without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why compareYieldHistoryTool is rated Low
This tool retrieves and analyzes historical data about cryptocurrency yield pools. The verbs 'compares' and 'analyzing' indicate data inspection only. There is no creation, modification, deletion, or execution of code/transactions. The most severe capability on this server appears to be depositWETH (Write/Financial), but this specific tool remains Read-category.
From the tool's definition Tool description states it 'Compares historical yield performance across multiple pools, analyzing metrics like APY, volatility, and TVL trends' — purely analytical/informational operations with no side effects.
Attacks that exploit this kind of access
The rule that runs compareYieldHistoryTool safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agentek Eth, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For compareYieldHistoryTool, this is the rule to start with:
compareYieldHistoryTool 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 Agentek Eth, apply this rule, and every compareYieldHistoryTool call is checked against it from then on.
Questions about compareYieldHistoryTool
Compares historical yield performance across multiple pools, analyzing metrics like APY, volatility, and TVL trends. It is categorised as a Read tool in the Agentek Eth MCP Server, which means it retrieves data without modifying state.
Register the Agentek Eth MCP server in PolicyLayer and add a rule for compareYieldHistoryTool: 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 Agentek Eth. Nothing to install.
compareYieldHistoryTool 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 compareYieldHistoryTool 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 compareYieldHistoryTool. 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.
compareYieldHistoryTool is provided by the Agentek Eth MCP server (nanidao/agentek). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agentek Eth, and thousands of servers like it.
This server
Across the catalogue