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 obser...
This record as markdown: /tools/com-funding-radar-radar/settlement-calendar.md
What settlement_calendar does on Radar
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
lang | string | — | Language of the summary and links: 'en' (default) or 'ru' |
horizonHours | integer | — | Horizon in hours, 1–8, default 4 |
Parameters from the server's own tool schema.
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.
Attacks that exploit this kind of access
The rule that runs settlement_calendar safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Radar, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For settlement_calendar, this is the rule to start with:
settlement_calendar 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 Radar, apply this rule, and every settlement_calendar call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Radar MCP Server, which means it retrieves data without modifying state.
settlement_calendar accepts 2 parameters: lang, horizonHours. The full parameter table on this page comes from the server's own tool schema.
Register the Radar MCP server in PolicyLayer and add a rule for settlement_calendar: 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 Radar. Nothing to install.
settlement_calendar 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 settlement_calendar 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 settlement_calendar. 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.
settlement_calendar is provided by the Radar MCP server (https://funding-radar.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Radar, and thousands of servers like it.
This server
Across the catalogue