tab_race
Get TAB race details. A race is addressed by its meeting date, meeting name, and race number (TAB has no single race id).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/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_type | string | — | R (thoroughbred), G (greyhound), or H (harness). Default R. |
race_number | string | Yes | Race number within the meeting |
jurisdiction | string | — | State jurisdiction, e.g. VIC (default), NSW. |
meeting_date | string | Yes | Meeting date, YYYY-MM-DD |
meeting_name | string | Yes | Meeting name, e.g. Flemington |
Parameters from the server's own tool schema.
Why tab_race is rated Low
This tool retrieves read-only information about TAB (Totalisator Agency Board) races. It performs a lookup/query operation without side effects, modifications, deletions, or execution of arbitrary code. The worst case for misuse would be information disclosure, which is low severity.
From the tool's definition Tool description states 'Get TAB race details' — a retrieval operation with no modification or execution capability. The tool queries racing information by meeting date, meeting name, and race number.
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. A race is addressed by its meeting date, meeting name, and race number (TAB has no single race id). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
tab_race accepts 6 parameters: api_key, race_type, race_number, jurisdiction, meeting_date, meeting_name. Required: race_number, meeting_date, meeting_name. 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 (@unclick/mcp-server). 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