Find the highest-yielding DeFi opportunities across Aave, Compound, Curve, Yearn, Morpho, and 100+ protocols. Returns APY, TVL, risk rating, and protocol audit status. Use this tool when: - A DeFi agent is allocating capital and wants to find the best risk-adjusted yield - You need to compare yie...
AI agents call get_defi_yields to retrieve information from Omni Service Node without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure data retrieval tool that queries and aggregates existing DeFi protocol metrics. While the server context mentions financial operations (USDC on Base via x402), this specific tool only reads and compares publicly available yield data to inform decision-making. It does not execute trades, move funds, or commit financial obligations—it merely returns comparative information.
From the tool's definition Tool retrieves DeFi yield data including APY, TVL, risk rating, and audit status across protocols. The description explicitly states it 'returns' information (protocol, asset, chain, apy, tvl_usd, apy_type) with no modification, creation, or execution…
Attacks that exploit this kind of access
Find the highest-yielding DeFi opportunities across Aave, Compound, Curve, Yearn, Morpho, and 100+ protocols. Returns APY, TVL, risk rating, and protocol audit status. Use this tool when: - A DeFi agent is allocating capital and wants to find the best risk-adjusted yield - You need to compare yield opportunities across multiple chains and protocols - An agent is rebalancing a yield portfolio and needs current APY data - You want to identify high APY opportunities with associated protocol risk ratings Returns per opportunity: protocol, asset, chain, apy, tvl_usd, apy_type (LENDING/LP/STAKING/VAULT), risk_rating (LOW/MEDIUM/HIGH), audited, reward_token. Example: getDefiYields({ chain:. It is categorised as a Read tool in the Omni Service Node MCP Server, which means it retrieves data without modifying state.
Register the Omni Service Node MCP server in PolicyLayer and add a rule for get_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 Omni Service Node. Nothing to install.
get_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 get_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 get_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.
get_defi_yields is provided by the Omni Service Node MCP server (luckkyyy23/omni-service-node). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →