clicks_get_yield_info
Get current yield protocol information: active protocol (Aave or Morpho), APYs, total balance, and total deposited across all agents.
This record as markdown: /tools/dev-bd37-clicks-protocol/clicks-get-yield-info.md
What clicks_get_yield_info does on Clicks Protocol
AI agents call clicks_get_yield_info to retrieve information from Clicks Protocol without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why clicks_get_yield_info is rated Low
This tool purely retrieves and queries existing data about yield protocols and agent balances. It has no side effects, does not create or modify data, and does not execute transactions or financial operations. Read-only query tools present minimal risk and fall squarely into the Read category with low severity.
From the tool's definition Tool description explicitly states it 'Get[s] current yield protocol information' including 'active protocol', 'APYs', 'total balance', and 'total deposited'. The server description confirms this is one of '4 read-only MCP tools'.
Attacks that exploit this kind of access
The rule that runs clicks_get_yield_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Clicks Protocol, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clicks_get_yield_info, this is the rule to start with:
clicks_get_yield_info 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 Clicks Protocol, apply this rule, and every clicks_get_yield_info call is checked against it from then on.
Questions about clicks_get_yield_info
Get current yield protocol information: active protocol (Aave or Morpho), APYs, total balance, and total deposited across all agents. It is categorised as a Read tool in the Clicks Protocol MCP Server, which means it retrieves data without modifying state.
Register the Clicks Protocol MCP server in PolicyLayer and add a rule for clicks_get_yield_info: 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 Clicks Protocol. Nothing to install.
clicks_get_yield_info 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 clicks_get_yield_info 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 clicks_get_yield_info. 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.
clicks_get_yield_info is provided by the Clicks Protocol MCP server (dev-bd37/clicks-protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Clicks Protocol, and thousands of servers like it.
This server
Across the catalogue