Fetch incident data (collisions, penalties, etc.) from a session. Optionally filter by driver.
AI agents call list_incidents 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 and queries existing Formula 1 incident data without modifying, creating, deleting, or executing any operations. It is analogous to other sibling read operations on this server (list_drivers, list_laps, list_pit_stops). The optional filtering by driver does not change the fundamental read-only nature.
From the tool's definition Tool name 'list_incidents' and description 'Fetch incident data' indicate a retrieval operation. The verb 'Fetch' and the action of querying historical incident records (collisions, penalties) from a session are read-only operations with no side effects.
Attacks that exploit this kind of access
Fetch incident data (collisions, penalties, etc.) 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_incidents: 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_incidents 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_incidents 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_incidents. 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_incidents 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 →