AI agents call dirty_air_loss_estimation 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 performs telemetry analysis and calculates aerodynamic metrics from existing race data. It retrieves or computes values for analysis purposes without creating, modifying, deleting, or executing external code. The estimation output has no side effects on any system or data store.
From the tool's definition Tool name contains 'estimation' and description states 'Estimate aerodynamic efficiency loss', indicating data retrieval and analysis without modification or execution of external systems.
Attacks that exploit this kind of access
Estimate aerodynamic efficiency loss from dirty air on a lap. 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 dirty_air_loss_estimation: 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.
dirty_air_loss_estimation 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 dirty_air_loss_estimation 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 dirty_air_loss_estimation. 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.
dirty_air_loss_estimation 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 →