openf1_get_drivers
Get driver information for a session or across sessions. Returns driver names, numbers, team names, and more.
This record as markdown: /tools/io-github-lacausecrypto-sports-hub/openf1-get-drivers.md
What openf1_get_drivers does on Sports Hub
AI agents call openf1_get_drivers to retrieve information from Sports Hub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why openf1_get_drivers is rated Low
This tool retrieves static or session-based driver metadata from a Formula 1 API. There are no side effects, no data modification, no code execution, and no financial implications. The blast radius of misuse is minimal—an AI agent cannot harm systems or users by fetching driver information. Confidence is high because the description unambiguously describes a data retrieval operation.
From the tool's definition Tool description states it 'Get[s] driver information' and 'Returns driver names, numbers, team names, and more.' The verb 'Get' and the passive nature of returning pre-existing data indicate a read-only operation with no modification, deletion, or execution…
Attacks that exploit this kind of access
The rule that runs openf1_get_drivers safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sports Hub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openf1_get_drivers, this is the rule to start with:
openf1_get_drivers 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 Sports Hub, apply this rule, and every openf1_get_drivers call is checked against it from then on.
Questions about openf1_get_drivers
Get driver information for a session or across sessions. Returns driver names, numbers, team names, and more. It is categorised as a Read tool in the Sports Hub MCP Server, which means it retrieves data without modifying state.
Register the Sports Hub MCP server in PolicyLayer and add a rule for openf1_get_drivers: 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 Sports Hub. Nothing to install.
openf1_get_drivers 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 openf1_get_drivers 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 openf1_get_drivers. 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.
openf1_get_drivers is provided by the Sports Hub MCP server (mcp-sports-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sports Hub, and thousands of servers like it.
This server
Across the catalogue