F1

122 tools. 6 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated:

6 can modify or destroy data
116 read-only
122 tools total

Community server · catalogue entry verified 03/07/2026

How to control F1 ↓

What F1 exposes to your agents

Read (116) Write / Execute (5) Destructive / Financial (1)
Critical Risk

The most dangerous F1 tools

6 of F1's 122 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control F1

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

Deny destructive operations
{
  "clear_cache": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "fill_missing_telemetry": {
    "limits": [
      {
        "counter": "fill_missing_telemetry_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "braking_point_analysis": {
    "limits": [
      {
        "counter": "braking_point_analysis_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 F1 — 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 F1 →

Instant setup, no code required.

All 122 F1 tools

READ 116 tools
Read braking_point_analysis Analyze braking events and average brake pressure for a lap. Read cache_stats Returns cached sessions in memory Read compare_lap_telemetry Compare speed traces between two driver-lap combinations. Read compare_tyre_performance Compare average and best lap times across tyre compounds. Read corner_apex_speed Get minimum speed through a corner's apex. Read corner_entry_speed Get average speed in the braking zone before a corner. Read corner_exit_speed Get average speed in the acceleration zone after a corner. Read corner_speed_comparison Compare corner entry, apex, and exit speeds between two drivers. Read dirty_air_loss_estimation Estimate aerodynamic efficiency loss from dirty air on a lap. Read downforce_estimation Estimate relative downforce level based on speed-gear stability. Read driver_aggression_index Calculate an aggression index based on overtake frequency. Read driver_consistency_score Calculate a 0-1 consistency score based on lap time variance. Read driver_risk_index Calculate a risk index based on deleted lap frequency. Read driver_style_clustering Cluster drivers into driving style groups using K-means. Read energy_deployment_pattern Analyze ERS energy deployment events and acceleration patterns. Read find_max_speed Find the maximum speed achieved during a lap. Read find_min_speed_corner Find the lowest speed point (slowest corner) during a lap. Read generate_race_progression_chart Generate a position vs lap chart for a driver's race. Read generate_sector_performance_chart Generate a bar chart of average sector times for a driver. Read generate_track_dominance_map Generate a speed comparison overlay plot for two drivers. Read generate_tyre_degradation_plot Generate a lap time progression plot showing tyre degradation. Read get_all_laps Get all lap data for every driver in a session. Read get_average_stint_length Get the average stint length across all drivers in laps. Read get_battle_detection Detect close battles between drivers within a gap threshold. Read get_best_sector_times Get the best sector times across all drivers in the session. Read get_brake_trace Get brake application values across a lap. Read get_circuit_info Get circuit corner positions, marshal lights, and marshal sectors. Read get_clean_laps Get only clean laps (green track status) for a driver. Read get_constructor_standings Get constructor championship standings for a season. Read get_corner_telemetry Get telemetry data around a specific corner (+/- 50m). Read get_deleted_laps Get laps that were deleted (track limits) for a driver. Read get_distance_telemetry Get distance-from-start values across a lap. Read get_driver_best_sectors Get a driver's personal best sector times in the session. Read get_driver_finish_position Get a driver's finishing position in a session. Read get_driver_grid_position Get a driver's starting grid position for a session. Read get_driver_info Get detailed driver metadata including name, team, and number. Read get_driver_laps Get all lap data for a specific driver in a session. Read get_driver_number Get the car number for a specific driver. Read get_driver_points Get the points scored by a driver in a session. Read get_driver_race_progression Get a driver's position on every lap throughout the race. Read get_driver_standings Get driver championship standings for a season. Read get_driver_team Get the team name for a specific driver. Read get_drs_usage Get DRS activation status across a lap. Read get_fastest_lap Get the fastest lap of the session with driver and time. Read get_gap_between_drivers Get the lap time gap between two drivers on every lap. Read get_gap_to_leader Get a driver's time gap to the race leader on every lap. Read get_gear_trace Get gear selection values across a lap. Read get_lap_delta Get the lap time difference between two drivers on a specific lap. Read get_lap_leader Get the race leader on a specific lap. Read get_lap_position Get a driver's race position on a specific lap. Read get_lap_telemetry Get full car telemetry data for a specific lap. Read get_lap_time Get the lap time for a specific driver on a specific lap. Read get_lap_time_distribution Get statistical distribution of lap times across the session. Read get_lap_times_series Get the full series of lap times for a driver across the session. Read get_overtakes Detect all overtaking moves with driver, lap, and positions gained. Read get_pit_lane_loss Get the average time lost in the pit lane versus a clean lap. Read get_pit_stop_time Get pit stop durations for a driver across their stops. Read get_pit_stops Get all pit stops in the session with driver, lap, and compound. Read get_position_changes Get positions gained, lost, and net change for all drivers. Read get_race_lead_changes Get all lead changes during the race with lap and new leader. Read get_rpm_trace Get engine RPM values across a lap. Read get_safety_car_periods Get safety car, VSC, and red flag periods with timing. Read get_sector_delta Get the sector time deltas between two drivers on a specific lap. Read get_sector_times Get sector times for a driver on a specific lap. Read get_session_flag_events Get all flag and track status events during a session. Read get_session_info Get metadata for a session including event name, location, and date. Read get_session_start_time Get the official start time of a session. Read get_session_weather Get weather data recorded during the session. Read get_speed_trace Get speed values across a lap as an array. Read get_stints Get stint breakdown with compound and lap count for a driver. Read get_teammate Find the teammate of a driver based on team assignment. Read get_telemetry_segment Get telemetry data for a specific distance segment of a lap. Read get_throttle_trace Get throttle application values across a lap. Read get_track_layout Get corner positions and distances for the track layout. Read get_track_length Get approximate track length in meters. Read get_track_status_changes Get track status transitions (green, yellow, red, SC, VSC). Read get_tyre_compound_usage Get total lap count per tyre compound across the session. Read get_tyre_degradation_rate Get lap time degradation slope per compound for a driver. Read get_tyre_strategy Get a driver's tyre strategy with compounds and stint details. Read lap_time_variance Get the statistical variance of a driver's lap times. Read list_drivers List all drivers participating in a session with codes and names. Read list_grand_prix List all Grand Prix events for a given season. Read list_seasons List all F1 seasons available in the FastF1 database. Read list_sessions List available sessions (FP1, FP2, FP3, Q, R) for a Grand Prix. Read merge_fastf1_and_ergast_results Merge FastF1 session results with Ergast standings data. Read optimal_pit_window Find the optimal pit stop lap based on rolling lap time average. Read overcut_effectiveness Measure pace gain from pitting late (overcut) for a driver. Read performance_trend Detect whether a driver's pace is improving, stable, or declining. Read pit_stop_summary Get pit stop count and laps for all drivers in the session. Read predict_battle_outcome Predict which driver will win a head-to-head battle. Read predict_driver_position_end_of_race Predict a driver's finishing position from position trend. Read predict_lap_time Predict a driver's next lap time using linear regression. Read predict_next_pit_stop Predict a driver's next pit stop lap based on stint intervals. Read predict_optimal_strategy Recommend optimal pit strategy based on tyre degradation rate. Read predict_overcut_success Predict whether an overcut strategy would be effective for a driver. Read predict_overtake_probability Predict the probability of one driver overtaking another. Read predict_race_podium Predict the top 3 finishers based on average race pace. Read predict_race_winner Predict the race winner based on average lap pace. Read predict_safety_car_probability Estimate the probability of a safety car deployment. Read predict_tyre_cliff Predict the lap where each tyre compound's performance drops off. Read predict_tyre_strategy Predict a driver's likely tyre strategy type. Read predict_undercut_success Predict whether an undercut strategy would be effective for a driver. Read predict_virtual_safety_car_probability Estimate the probability of a VSC deployment. Read preload_driver_telemetry Preload all lap telemetry for a driver into cache. Read provider_health_check Check health status of session cache, telemetry cache, and Ergast API. Read qualifying_improvement_analysis Measure a driver's lap time improvement across qualifying. Read sector_consistency Get sector time standard deviation as a consistency metric. Read sector_delta_vs_teammate Get average sector time deltas between a driver and their teammate. Read sector_improvement_over_time Get sector time improvement from first to last lap for a driver. Read sector_performance_summary Get best, average, and median sector times for a driver. Read telemetry_available Check if telemetry data is available for a driver in a session. Read throttle_application_analysis Analyze throttle usage statistics for a lap. Read track_position_importance Measure how much track position correlates with lap time. Read tyre_strategy_comparison Compare tyre strategies between two drivers side by side. Read undercut_effectiveness Measure pace gain from pitting early (undercut) for a driver. Read validate_session_data Check if session data loaded correctly.

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about F1

Can an AI agent delete data through the F1 MCP server? +

Yes. The F1 server exposes 1 destructive tools including clear_cache. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through F1? +

The F1 server has 3 write tools including fill_missing_telemetry, generate_lap_delta_plot, generate_speed_map. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach F1.

How many tools does the F1 MCP server expose? +

122 tools across 4 categories: Destructive, Execute, Read, Write. 116 are read-only. 6 can modify, create, or delete data.

How do I enforce a policy on F1? +

Register the F1 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 F1 tool call.

Deterministic rules across all 122 F1 tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

122 F1 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.