crypto.defi-yields
DeFi yield & lending rates across protocols (via DefiLlama, free/keyless). Returns pools ranked by APY or TVL with base vs reward APY, TVL, 1d/7d/30d APY trend, stablecoin flag, and IL-risk. Filter by chain, project (aave, compound, lido…), symbol (USDC, ETH…), minApy, minTvlUsd. The yield/lendin...
This record as markdown: /tools/io-github-2s-io-mcp/crypto.defi-yields.md
What crypto.defi-yields does on Mcp
AI agents call crypto.defi-yields 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-yields is rated Low
This is a data query tool that retrieves DeFi protocol information (APY, TVL, trends, risk flags) from an external API. While the server itself is 'pay-per-call tools settled in USDC' and involves crypto, this specific tool does not execute financial transactions, move money, or modify any on-chain or off-chain state. It only reads and returns yield farming data.
From the tool's definition Tool description states it 'Returns pools ranked by APY or TVL' with filtering capabilities. Uses DefiLlama data (free/keyless access). No mention of executing trades, moving funds, or modifying any state—purely data retrieval of yield rates and TVL metrics.
Attacks that exploit this kind of access
The rule that runs crypto.defi-yields 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-yields, this is the rule to start with:
crypto.defi-yields 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-yields call is checked against it from then on.
Questions about crypto.defi-yields
DeFi yield & lending rates across protocols (via DefiLlama, free/keyless). Returns pools ranked by APY or TVL with base vs reward APY, TVL, 1d/7d/30d APY trend, stablecoin flag, and IL-risk. Filter by chain, project (aave, compound, lido…), symbol (USDC, ETH…), minApy, minTvlUsd. The yield/lending-rate layer beyond crypto.defi\. 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-yields: 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-yields 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-yields 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-yields. 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-yields 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