# clicks_get_referral_stats

Get referral network stats for an agent: direct referrals count, total earned from referrals, claimable rewards, and referral chain.

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

## Facts

- Tool: `clicks_get_referral_stats`
- 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: 1
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `agent_address` | string | no | Ethereum address of the AI agent |

Parameters from the server's own tool schema.

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

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

## Why clicks_get_referral_stats is rated Low

This tool queries and retrieves existing data about referral statistics without creating, modifying, executing, or deleting anything. It is purely informational retrieval. The server description confirms 'read-only' classification, and the tool returns only analytics data.

From the tool's own definition: "Tool retrieves 'referral network stats' including 'direct referrals count, total earned from referrals, claimable rewards, and referral chain' — all read-only data queries with no modification or execution capabilities."

## Use case

AI agents call clicks_get_referral_stats 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_referral_stats": {}
  }
}
```

## 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_yield_info` — Read — https://policylayer.com/tools/dev-bd37-clicks-protocol/clicks-get-yield-info.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