This record as markdown: /tools/creativelead-unclick/f1-positions.md
What f1_positions does on UnClick
AI agents call f1_positions 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 |
|---|---|---|---|
session_key | number | — | |
driver_number | number | — |
Parameters from the server's own tool schema.
Why f1_positions is rated Low
This tool retrieves Formula 1 position standings from a public sports data API. It queries and returns existing data without creating, modifying, deleting, or executing any operations with side effects. The read-only nature and public sports data source present minimal security risk.
From the tool's definition Tool name 'f1_positions' and description 'Get Formula 1 position data from OpenF1' indicate data retrieval with 'Get' verb and no modification or side effects.
Attacks that exploit this kind of access
The rule that runs f1_positions 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_positions, this is the rule to start with:
f1_positions 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_positions call is checked against it from then on.
Questions about f1_positions
Get Formula 1 position data from OpenF1. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
f1_positions accepts 2 parameters: session_key, driver_number. 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_positions: 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_positions 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_positions 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_positions. 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_positions 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