OpenF1 MCP Server

18 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated:

0 can modify or destroy data
18 read-only
18 tools total

Community server · catalogue entry verified 04/07/2026

How to control OpenF1 MCP Server ↓

What OpenF1 MCP Server exposes to your agents

Read (18) Write / Execute (0) Destructive / Financial (0)

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

How to control OpenF1 MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and OpenF1 MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations
{
  "get_available_tools": {
    "limits": [
      {
        "counter": "get_available_tools_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register OpenF1 MCP Server — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON OPENF1 →

Instant setup, no code required.

All 18 OpenF1 MCP Server tools

READ 18 tools
Read get_available_tools Get a list of all available tools provided by this MCP server. Read get_car_data Fetch car telemetry data (throttle, brake, DRS, etc.). Optionally filter by driver. Read get_constructor_standings Get constructor/team championship standings. Optionally filter by session_key. Read get_driver_standings Get driver championship standings. Optionally filter by session_key. Read get_server_status Get the current status of the MCP server, including version and availability. Read get_weather Fetch weather data for a session. Read list_drivers Fetch F1 drivers. Optionally filter by driver number. Read list_incidents Fetch incident data (collisions, penalties, etc.) from a session. Optionally filter by driver. Read list_laps Fetch lap data from a session. Optionally filter by driver. Read list_meetings Fetch F1 race meetings. Optionally filter by year. Read list_pit_stops Fetch pit stop data from a session. Optionally filter by driver. Read list_positions Fetch position data (live positions during session). Optionally filter by driver. Read list_races Fetch F1 races. Optionally filter by year. Read list_results Fetch race results. Optionally filter by session or driver. Read list_sessions Fetch F1 sessions (practice, qualifying, race). Optionally filter by session_key or meeting_key. Read list_stints Fetch stint data (tire stints). Optionally filter by driver. Read list_teams Fetch F1 teams. Read verify_client_connection Verify that the client is properly connected to the MCP server.

Questions about OpenF1 MCP Server

Is the OpenF1 MCP Server MCP server safe to use without restrictions? +

The OpenF1 MCP Server server is primarily read-only with 18 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the OpenF1 MCP Server MCP server expose? +

18 tools across 1 categories: Read. 18 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on OpenF1 MCP Server? +

Register the OpenF1 MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every OpenF1 MCP Server tool call.

Deterministic rules across all 18 OpenF1 MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

18 OpenF1 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.