pair_briefing
Everything the radar knows about one perpetual pair in a single answer: funding rate and receiving side, time to next settlement, mark price, 24h volume, open interest with deviation from the 7-day norm, orderbook walls with break-through history, how the price usually moves around settlement, an...
This record as markdown: /tools/com-funding-radar-radar/pair-briefing.md
What pair_briefing does on Radar
AI agents call pair_briefing 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' |
symbol | string | Yes | Native pair symbol (BTCUSDT, BTC-USDT-SWAP) or base coin (BTC) |
exchange | string | Yes | Exchange id |
Parameters from the server's own tool schema.
Why pair_briefing is rated Low
Even though pair_briefing 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 pair_briefing 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 pair_briefing, this is the rule to start with:
pair_briefing 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 pair_briefing call is checked against it from then on.
Questions about pair_briefing
Everything the radar knows about one perpetual pair in a single answer: funding rate and receiving side, time to next settlement, mark price, 24h volume, open interest with deviation from the 7-day norm, orderbook walls with break-through history, how the price usually moves around settlement, and the same coin on other exchanges. Accepts an exact symbol (BTCUSDT) or just the coin (BTC). It is categorised as a Read tool in the Radar MCP Server, which means it retrieves data without modifying state.
pair_briefing accepts 3 parameters: lang, symbol, exchange. Required: symbol, exchange. 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 pair_briefing: 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.
pair_briefing 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 pair_briefing 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 pair_briefing. 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.
pair_briefing 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