f1_pit_stops

Get Formula 1 pit stop data from OpenF1.

SERVERUnClick SOURCE@unclick/mcp-server

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/f1-pit-stops.md

WHAT IT DOES

What f1_pit_stops does on UnClick

AI agents call f1_pit_stops to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`session_key`	number	Yes
`driver_number`	number	—

Parameters from the server's own tool schema.

RISK

Why f1_pit_stops is rated Low

This tool retrieves historical or current Formula 1 pit stop statistics from an external API (OpenF1). The verb 'Get' and the passive data source (OpenF1) confirm it is a read-only operation with no side effects, no code execution, and no ability to modify or delete data. The blast radius of misuse is minimal—an AI agent could only query public sports data.

From the tool's definition Tool name 'f1_pit_stops' and description 'Get Formula 1 pit stop data from OpenF1' indicate data retrieval with no modification capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs f1_pit_stops safely

PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For f1_pit_stops, this is the rule to start with:

f1_pit_stops Allowed

f1_pit_stops is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "f1_pit_stops": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every f1_pit_stops call is checked against it from then on.

FAQ

Questions about f1_pit_stops

What does the f1_pit_stops tool do? +

Get Formula 1 pit stop data from OpenF1. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.

What parameters does f1_pit_stops accept? +

f1_pit_stops accepts 2 parameters: session_key, driver_number. Required: session_key. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on f1_pit_stops? +

Register the UnClick MCP server in PolicyLayer and add a rule for f1_pit_stops: 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 UnClick. Nothing to install.

What risk level is f1_pit_stops? +

f1_pit_stops is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit f1_pit_stops? +

Yes. Add a rate_limit block to the f1_pit_stops 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.

How do I block f1_pit_stops completely? +

Set action: deny in the PolicyLayer policy for f1_pit_stops. 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.

What MCP server provides f1_pit_stops? +

f1_pit_stops is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →