This record as markdown: /tools/creativelead-unclick/f1-sessions.md
What f1_sessions does on UnClick
AI agents call f1_sessions to retrieve information from UnClick 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 |
|---|---|---|---|
year | number | — | |
country_name | string | — | |
session_type | string | — |
Parameters from the server's own tool schema.
Why f1_sessions is rated Low
This tool only queries and returns F1 session information without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal security risk. Misuse by an AI agent would at worst retrieve unwanted public sports data, with no impact on systems, finances, or data integrity.
From the tool's definition Tool retrieves Formula 1 session data from OpenF1 API. The verb 'Get' and lack of any modification, deletion, or execution language indicate this is a data retrieval operation.
Attacks that exploit this kind of access
The rule that runs f1_sessions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For f1_sessions, this is the rule to start with:
f1_sessions 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 UnClick, apply this rule, and every f1_sessions call is checked against it from then on.
Questions about f1_sessions
Get Formula 1 sessions from OpenF1. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
f1_sessions accepts 3 parameters: year, country_name, session_type. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for f1_sessions: 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 UnClick. Nothing to install.
f1_sessions 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_sessions 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_sessions. 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_sessions is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue