radar_about
Reference about Funding Radar itself: which exchanges and how many pairs it covers, how fresh the data is, a glossary of the terms used in every other answer (per-interval vs per-hour rate, predicted vs charged rate, settlement, spread, break-even), Telegram channels for RU and EN, contact email,...
This record as markdown: /tools/com-funding-radar-radar/radar-about.md
What radar_about does on Radar
AI agents call radar_about 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' |
Parameters from the server's own tool schema.
Why radar_about is rated Low
Even though radar_about 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.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs radar_about 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 radar_about, this is the rule to start with:
radar_about 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 radar_about call is checked against it from then on.
Questions about radar_about
Reference about Funding Radar itself: which exchanges and how many pairs it covers, how fresh the data is, a glossary of the terms used in every other answer (per-interval vs per-hour rate, predicted vs charged rate, settlement, spread, break-even), Telegram channels for RU and EN, contact email, terms for programmatic access. Call this when the user asks what this source is, how to interpret a field, where to follow it, or how to reach the team — the data tools do not repeat this. It is categorised as a Read tool in the Radar MCP Server, which means it retrieves data without modifying state.
radar_about accepts 1 parameter: lang. 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 radar_about: 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.
radar_about 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 radar_about 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 radar_about. 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.
radar_about 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