Fetch lap data from a session. Optionally filter by driver.
AI agents call list_laps to retrieve information from OpenF1 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical lap timing and performance data from Formula 1 sessions. It has no side effects, cannot modify or delete data, and poses no financial or security risk. The operation is purely informational, consistent with other sibling tools like 'list_drivers', 'list_incidents', and 'list_pit_stops' which are all read operations against the openF1.org API.
From the tool's definition Tool name 'list_laps' and description 'Fetch lap data from a session' indicate data retrieval without modification. The verb 'fetch' combined with 'list' is characteristic of read-only operations.
Attacks that exploit this kind of access
Fetch lap data from a session. Optionally filter by driver. It is categorised as a Read tool in the OpenF1 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenF1 MCP Server MCP server in PolicyLayer and add a rule for list_laps: 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 OpenF1 MCP Server. Nothing to install.
list_laps 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 list_laps 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 list_laps. 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.
list_laps is provided by the OpenF1 MCP Server MCP server (jimmyjoe009/openf1_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 →