AI agents call f1_drivers to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
session_key | number | — | |
driver_number | number | — |
Parameters from the server's own tool schema.
This tool queries publicly available Formula 1 driver data from OpenF1 and returns information. No data is created, modified, deleted, executed, or committed financially. It is a simple read operation with negligible security risk.
From the tool's definition Tool name 'f1_drivers' and description 'Get Formula 1 driver info from OpenF1' indicate a data retrieval operation with the verb 'Get', which retrieves driver information without modification or side effects.
Attacks that exploit this kind of access
Get Formula 1 driver info from OpenF1. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
f1_drivers accepts 2 parameters: session_key, driver_number. 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_drivers: 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_drivers 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_drivers 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_drivers. 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_drivers 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →