funding_history
Charged funding rates of one coin across all exchanges where it trades, normalized to %/hour on a common hourly grid (up to 90 days back). Shows whether the cross-exchange spread is sustained (feeds a hedged pair) or a one-off spike. Returns the curves plus the median and maximum spread.
This record as markdown: /tools/com-funding-radar-radar/funding-history.md
What funding_history does on Radar
AI agents call funding_history 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 |
|---|---|---|---|
base | string | Yes | Base coin, e.g. BTC |
days | object | — | Window in days: 1, 3, 7 (default), 30 or 90 |
lang | string | — | Language of the summary and links: 'en' (default) or 'ru' |
Parameters from the server's own tool schema.
Why funding_history is rated Low
Even though funding_history 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 funding_history 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 funding_history, this is the rule to start with:
funding_history 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 funding_history call is checked against it from then on.
Questions about funding_history
Charged funding rates of one coin across all exchanges where it trades, normalized to %/hour on a common hourly grid (up to 90 days back). Shows whether the cross-exchange spread is sustained (feeds a hedged pair) or a one-off spike. Returns the curves plus the median and maximum spread. It is categorised as a Read tool in the Radar MCP Server, which means it retrieves data without modifying state.
funding_history accepts 3 parameters: base, days, lang. Required: base. 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 funding_history: 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.
funding_history 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 funding_history 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 funding_history. 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.
funding_history 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