# clicks_simulate_split

Preview how a USDC payment would be split for an agent: how much goes to wallet (liquid) and how much to DeFi yield.

Agent View of the PolicyLayer registry record for `clicks_simulate_split`. HTML page: https://policylayer.com/tools/dev-bd37-clicks-protocol/clicks-simulate-split

## Facts

- Tool: `clicks_simulate_split`
- 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: 2
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `amount` | string | no | Payment amount in USDC (e.g. "100" for 100 USDC) |
| `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_simulate_split",
    "arguments": {}
  }
}
```

## Why clicks_simulate_split is rated Low

This tool queries and returns a preview of a payment split calculation. It does not create, modify, delete, or execute any actual financial transactions. While it is DeFi-related, it performs no fund movement, no binding commitment, and no state change. Misuse by an agent would result in only viewing incorrect or misleading split scenarios, not financial loss or unauthorized transfers.

From the tool's own definition: "Tool description explicitly states 'Preview' and 'simulate' — it computes a hypothetical split without executing actual payments or transfers."

## Use case

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

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