Low Risk

get_defi_yields

Get top DeFi yield opportunities with quality scoring (A-F grades). Args: chain: Filter by chain (Ethereum, Base, Arbitrum) or empty for all min_tvl: Minimum TVL in USD (default 100000) limit: Max results (default 10)

Part of the AIGEN Agent Tools — Register, Collaborate, Build MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call get_defi_yields to retrieve information from AIGEN Agent Tools — Register, Collaborate, Build without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_defi_yields only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

aigen-agent-tools.yaml
tools:
  get_defi_yields:
    rules:
      - action: allow

See the full AIGEN Agent Tools — Register, Collaborate, Build policy for all 37 tools.

Tool Name get_defi_yields
Category Read
Risk Level Low

View all 37 tools →

Agents calling read-class tools like get_defi_yields have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the get_defi_yields tool do? +

Get top DeFi yield opportunities with quality scoring (A-F grades). Args: chain: Filter by chain (Ethereum, Base, Arbitrum) or empty for all min_tvl: Minimum TVL in USD (default 100000) limit: Max results (default 10) . It is categorised as a Read tool in the AIGEN Agent Tools — Register, Collaborate, Build MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_defi_yields? +

Add a rule in your Intercept YAML policy under the tools section for get_defi_yields. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AIGEN Agent Tools — Register, Collaborate, Build MCP server.

What risk level is get_defi_yields? +

get_defi_yields is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_defi_yields? +

Yes. Add a rate_limit block to the get_defi_yields rule in your Intercept 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.

How do I block get_defi_yields completely? +

Set action: deny in the Intercept 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.

What MCP server provides get_defi_yields? +

get_defi_yields is provided by the AIGEN Agent Tools — Register, Collaborate, Build MCP server (aigen/agent-tools). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on AIGEN Agent Tools — Register, Collaborate, Build

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.