funding_events
What is burning on the crypto perpetuals funding market right now: open extreme events (|hourly rate| ≥ 0.1%/h) with peaks and receiving sides, plus the top pairs by hourly funding rate across Binance, Bybit, OKX, Bitget and Hyperliquid. Rates are predictions for the next settlement; data age ≤ ~...
This record as markdown: /tools/com-funding-radar-radar/funding-events.md
What funding_events does on Radar
AI agents call funding_events 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' |
limit | integer | — | Rows per list, default 10 |
Parameters from the server's own tool schema.
Why funding_events is rated Low
Even though funding_events 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_events 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_events, this is the rule to start with:
funding_events 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_events call is checked against it from then on.
Questions about funding_events
What is burning on the crypto perpetuals funding market right now: open extreme events (|hourly rate| ≥ 0.1%/h) with peaks and receiving sides, plus the top pairs by hourly funding rate across Binance, Bybit, OKX, Bitget and Hyperliquid. Rates are predictions for the next settlement; data age ≤ ~5 min. It is categorised as a Read tool in the Radar MCP Server, which means it retrieves data without modifying state.
funding_events accepts 2 parameters: lang, limit. 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_events: 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_events 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_events 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_events. 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_events 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