AI agents call driver_consistency_score 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 tool performs analytical computation on historical F1 telemetry data (lap times) to derive a consistency metric. It reads data and returns a calculated value with no side effects, data modification, or system state changes. This is a classic Read operation—specifically, a retrieval and analysis function typical of analytics platforms.
From the tool's definition Tool name 'driver_consistency_score' and description 'Calculate a 0-1 consistency score based on lap time variance' indicate data retrieval and analysis with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Calculate a 0-1 consistency score based on lap time variance. 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 driver_consistency_score: 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.
driver_consistency_score 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 driver_consistency_score 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 driver_consistency_score. 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.
driver_consistency_score 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 →