AI agents call get_lap_delta 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 retrieves lap time deltas (differences) between drivers, which is a data lookup operation with no side effects. It does not modify data, execute arbitrary code, delete records, or trigger external operations. The function is purely informational/analytical, fitting the Read category. Severity is low as misuse would only expose comparative race analytics without operational impact.
From the tool's definition Tool name 'get_lap_delta' and description 'Get the lap time difference between two drivers on a specific lap' indicate a query operation that retrieves and compares existing telemetry data without modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get the lap time difference between two drivers on a specific lap. 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_lap_delta: 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_lap_delta 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_lap_delta 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_lap_delta. 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_lap_delta 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 →