Get results for a specific F1 session (practice, qualifying, or race)
AI agents call get_session_results to retrieve information from F1 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns historical F1 session results without creating, modifying, deleting, or executing operations. It has no side effects and presents minimal risk to data integrity or system state.
From the tool's definition Tool retrieves 'results for a specific F1 session' with no modification capability. The server description emphasizes 'retrieve and analyze F1 racing data' and the sibling tools (get_constructor_standings, get_driver_standings, get_lap_times,…
Attacks that exploit this kind of access
Get results for a specific F1 session (practice, qualifying, or race). It is categorised as a Read tool in the F1 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the F1 MCP Server MCP server in PolicyLayer and add a rule for get_session_results: 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 MCP Server. Nothing to install.
get_session_results 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_session_results 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_session_results. 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_session_results is provided by the F1 MCP Server MCP server (josh-mantel/mcp-f1). 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 →