AI agents call predict_virtual_safety_car_probability 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 analyzes historical or simulated race data to compute a statistical prediction. It reads telemetry or race parameters and outputs a probability estimate. There is no evidence of data modification, code execution, financial transactions, or destructive operations. It fits squarely in the Read category as a sports analytics query tool.
From the tool's definition Tool name contains 'predict' and description states 'Estimate the probability' — indicates a query/calculation operation that retrieves or derives predictive analytics from existing Formula 1 race data without modifying, executing external operations, or…
Attacks that exploit this kind of access
Estimate the probability of a VSC deployment. 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 predict_virtual_safety_car_probability: 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.
predict_virtual_safety_car_probability 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 predict_virtual_safety_car_probability 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 predict_virtual_safety_car_probability. 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.
predict_virtual_safety_car_probability 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 →