This record as markdown: /tools/creativelead-unclick/tab-race.md
What tab_race does on UnClick
AI agents call tab_race 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 |
|---|---|---|---|
api_key | string | — | |
race_id | string | — |
Parameters from the server's own tool schema.
Why tab_race is rated Low
This tool retrieves information about horse racing events and details from TAB. It performs a simple query with no side effects, no code execution, no financial transactions, and no data modifications. It fits the Read category definition: 'retrieves or queries data; no side effects'.
From the tool's definition Tool name 'tab_race' with description 'Get TAB race details' indicates a retrieval operation. The verb 'Get' and the read-only nature of querying race details (TAB is The Australian Racing Board) shows no data modification, deletion, or execution of external…
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs tab_race 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 tab_race, this is the rule to start with:
tab_race 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 tab_race call is checked against it from then on.
Questions about tab_race
Get TAB race details. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
tab_race accepts 2 parameters: api_key, race_id. 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 tab_race: 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.
tab_race 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 tab_race 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 tab_race. 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.
tab_race 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