Fetch stint data (tire stints). Optionally filter by driver.
AI agents call list_stints 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 or current stint (tire strategy) data from the Formula 1 API without modifying, deleting, or executing operations. It is purely a read operation that queries existing data, similar to sibling tools like 'list_drivers', 'list_laps', and 'list_incidents'. Misuse by an AI agent would result in information disclosure only, with no destructive, financial, or operational impact.
From the tool's definition Tool is named 'list_stints' and described as 'Fetch stint data (tire stints). Optionally filter by driver.' The use of 'Fetch' and 'list' indicates data retrieval with optional filtering; no modification, deletion, or code execution is implied.
Attacks that exploit this kind of access
Fetch stint data (tire stints). 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_stints: 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_stints 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_stints 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_stints. 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_stints 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 →