# clicks_get_yield_info

Get current yield protocol information: active protocol (Aave or Morpho), APYs, total balance, and total deposited across all agents.

Agent View of the PolicyLayer registry record for `clicks_get_yield_info`. HTML page: https://policylayer.com/tools/dev-bd37-clicks-protocol/clicks-get-yield-info

## Facts

- Tool: `clicks_get_yield_info`
- Server: Clicks Protocol (`dev-bd37/clicks-protocol`) — https://policylayer.com/tools/dev-bd37-clicks-protocol.md
- Homepage: https://github.com/dev-bd37/clicks-protocol
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "clicks_get_yield_info",
    "arguments": {}
  }
}
```

## 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 own 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'."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Clicks Protocol:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "clicks_get_yield_info": {}
  }
}
```

## Other tools on Clicks Protocol (3)

- `clicks_get_agent_info` — Read — https://policylayer.com/tools/dev-bd37-clicks-protocol/clicks-get-agent-info.md
- `clicks_get_referral_stats` — Read — https://policylayer.com/tools/dev-bd37-clicks-protocol/clicks-get-referral-stats.md
- `clicks_simulate_split` — Read — https://policylayer.com/tools/dev-bd37-clicks-protocol/clicks-simulate-split.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dev-bd37-clicks-protocol · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-bd37-clicks-protocol