AI agents call get_driver_race_progression to retrieve information from F1 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward data retrieval tool that queries and returns telemetry/race progression information. It has no side effects, does not modify data, does not execute code or commands, and does not perform irreversible actions. The blast radius of misuse is minimal—returning incorrect race data poses no security risk beyond potential misinformation.
From the tool's definition Tool retrieves 'a driver's position on every lap throughout the race' - a query operation that accesses historical race data without modification, deletion, or execution of external operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get a driver's position on every lap throughout the race. It is categorised as a Read tool in the F1 MCP Server, which means it retrieves data without modifying state.
Register the F1 MCP server in PolicyLayer and add a rule for get_driver_race_progression: 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 F1. Nothing to install.
get_driver_race_progression 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 get_driver_race_progression 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 get_driver_race_progression. 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.
get_driver_race_progression is provided by the F1 MCP server (luffy610/f1-mcp). 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 →