AI agents call get_throttle_trace 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 retrieves throttle telemetry data from a Formula 1 race analysis database. It performs a data query with no side effects, no code execution, no modifications to any system, and no destructive operations. It is purely informational/analytical in nature, consistent with other sibling tools like 'corner_apex_speed' and 'corner_entry_speed' that also retrieve telemetry metrics.
From the tool's definition Tool name 'get_throttle_trace' and description 'Get throttle application values across a lap' indicate a retrieval operation that queries telemetry data.
Attacks that exploit this kind of access
Get throttle application values across 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 get_throttle_trace: 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_throttle_trace 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_throttle_trace 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_throttle_trace. 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_throttle_trace 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 →