f1.races.results
Get the finishing results for a specific Formula 1 race: final classified positions, driver name, constructor, grid position, laps completed, finish status (Finished/DNF/DSQ/+N Laps), points scored, finish time, and fastest lap time and rank. Defaults to the most recently completed race (round=la...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/f1.races.results.md
What f1.races.results does on Apibase
AI agents call f1.races.results to retrieve information from Apibase 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 |
|---|---|---|---|
limit | integer | — | Maximum number of results to return (1–100, default 30). |
round | string | number | — | Race round number within the season (1-based), or 'last' for the most recent completed race. Omit for last race. |
offset | integer | — | Pagination offset — number of results to skip (default 0). |
season | string | number | — | Season year (e.g. 2026, 2024, 2023). Omit for the current season. |
Parameters from the server's own tool schema.
Why f1.races.results is rated Low
Retrieves historical F1 race data with no side effects or state mutations.
From the tool's definition Get the finishing results for a specific Formula 1 race: final classified positions, driver name, constructor, grid position, laps completed, finish status, points scored, finish time, and fastest lap time and rank.
Attacks that exploit this kind of access
The rule that runs f1.races.results safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For f1.races.results, this is the rule to start with:
f1.races.results is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every f1.races.results call is checked against it from then on.
Questions about f1.races.results
Get the finishing results for a specific Formula 1 race: final classified positions, driver name, constructor, grid position, laps completed, finish status (Finished/DNF/DSQ/+N Laps), points scored, finish time, and fastest lap time and rank. Defaults to the most recently completed race (round=last) of the current season. Specify season + round to fetch any race back to 1950. Data source: Jolpica F1 (Ergast-compatible API) — free, unlimited, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
f1.races.results accepts 4 parameters: limit, round, offset, season. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for f1.races.results: 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 Apibase. Nothing to install.
f1.races.results 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 f1.races.results 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 f1.races.results. 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.
f1.races.results is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue