# settlement_calendar

Which notable funding settlements are coming in the next hours (default 4): pairs with |rate| ≥ 0.05%/h and volume ≥ $1M, sorted by time. Each row includes that pair's own settlement-window statistics — how much its price usually moves in the 15 minutes before the charge, with the number of observed windows.

Agent View of the PolicyLayer registry record for `settlement_calendar`. HTML page: https://policylayer.com/tools/com-funding-radar-radar/settlement-calendar

## Facts

- Tool: `settlement_calendar`
- Server: Radar (`https://funding-radar.com/mcp`) — https://policylayer.com/tools/com-funding-radar-radar.md
- Homepage: https://github.com/https://funding-radar.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 2
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `lang` | string | no | Language of the summary and links: 'en' (default) or 'ru' |
| `horizonHours` | integer | no | Horizon in hours, 1–8, default 4 |

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": "settlement_calendar",
    "arguments": {}
  }
}
```

## Why settlement_calendar is rated Low

Even though settlement_calendar only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call settlement_calendar to retrieve information from Radar 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 Radar:

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

## Other tools on Radar (5)

- `funding_events` — Read — https://policylayer.com/tools/com-funding-radar-radar/funding-events.md
- `funding_history` — Read — https://policylayer.com/tools/com-funding-radar-radar/funding-history.md
- `pair_briefing` — Read — https://policylayer.com/tools/com-funding-radar-radar/pair-briefing.md
- `radar_about` — Read — https://policylayer.com/tools/com-funding-radar-radar/radar-about.md
- `spread_pairs` — Read — https://policylayer.com/tools/com-funding-radar-radar/spread-pairs.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=com-funding-radar-radar · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-funding-radar-radar