openf1_get_stints

Get stint data including tire compound, stint number, lap counts, and tire age for each driver.

SERVERSports Hub SOURCEmcp-sports-hub

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/io-github-lacausecrypto-sports-hub/openf1-get-stints.md

WHAT IT DOES

What openf1_get_stints does on Sports Hub

AI agents call openf1_get_stints 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.

RISK

Why openf1_get_stints is rated Low

This is a straightforward query/retrieval tool that fetches historical or current stint statistics from a Formula 1 API. It does not modify data, execute code, delete records, or involve financial transactions. The blast radius of misuse is minimal—an attacker could only retrieve publicly available sports data.

From the tool's definition Tool retrieves stint data (tire compound, stint number, lap counts, tire age) for drivers. The verb 'get' and the data-retrieval nature indicate no modification or side effects. No deletion, execution of code, or financial operations are implied.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs openf1_get_stints 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_stints, this is the rule to start with:

openf1_get_stints Allowed

openf1_get_stints 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": {
    "openf1_get_stints": {}
  }
}

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

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

FAQ

Questions about openf1_get_stints

What does the openf1_get_stints tool do? +

Get stint data including tire compound, stint number, lap counts, and tire age for each driver. It is categorised as a Read tool in the Sports Hub MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on openf1_get_stints? +

Register the Sports Hub MCP server in PolicyLayer and add a rule for openf1_get_stints: 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.

What risk level is openf1_get_stints? +

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

Can I rate-limit openf1_get_stints? +

Yes. Add a rate_limit block to the openf1_get_stints 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 openf1_get_stints completely? +

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

openf1_get_stints 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.

KEEP EXPLORING

More on Sports Hub, and thousands of servers like it.

This server

All 396 Sports Hub tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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