f1_team_radio
Get Formula 1 team radio messages from OpenF1.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/f1-team-radio.md
What f1_team_radio does on UnClick
AI agents call f1_team_radio to retrieve information from UnClick 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 |
|---|---|---|---|
session_key | number | Yes | |
driver_number | number | — |
Parameters from the server's own tool schema.
Why f1_team_radio is rated Low
The tool retrieves historical or live Formula 1 team radio data from OpenF1 API. This is a read-only operation that queries existing data without side effects. There is no capability to modify, delete, or execute commands. Severity is low because misuse would only result in unauthorized data access to publicly available sports telemetry, with minimal blast radius.
From the tool's definition Tool description states 'Get Formula 1 team radio messages' — this is a retrieval operation with no modification, deletion, or execution of external systems.
Attacks that exploit this kind of access
The rule that runs f1_team_radio safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For f1_team_radio, this is the rule to start with:
f1_team_radio 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 UnClick, apply this rule, and every f1_team_radio call is checked against it from then on.
Questions about f1_team_radio
Get Formula 1 team radio messages from OpenF1. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
f1_team_radio accepts 2 parameters: session_key, driver_number. Required: session_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for f1_team_radio: 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 UnClick. Nothing to install.
f1_team_radio 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 f1_team_radio 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 f1_team_radio. 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.
f1_team_radio is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue