AI agents call get_tyre_degradation_rate 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 queries historical F1 telemetry/analytics data to compute degradation metrics. It reads existing race data and returns analytical results without creating, modifying, or destructively changing any information. No code execution, financial transactions, or irreversible actions are involved.
From the tool's definition Tool retrieves and analyzes tyre degradation rate data: 'Get lap time degradation slope per compound for a driver' - purely a data query with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get lap time degradation slope per compound for a driver. 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 get_tyre_degradation_rate: 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.
get_tyre_degradation_rate 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_tyre_degradation_rate 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_tyre_degradation_rate. 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_tyre_degradation_rate 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 →