This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/tab-meetings.md
What tab_meetings does on UnClick
AI agents call tab_meetings 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 |
|---|---|---|---|
date | string | — | YYYY-MM-DD |
api_key | string | — | |
jurisdiction | string | — | e.g. VIC, NSW |
Parameters from the server's own tool schema.
Why tab_meetings is rated Low
This tool retrieves race meeting information from TAB (Totalisator Agency Board) for a given date. It performs no modification, deletion, execution, or financial transaction. The operation is a simple query with no side effects, making it a Read category tool with low severity risk.
From the tool's definition Tool name 'tab_meetings' and description 'Get TAB race meetings for a date' indicate a data retrieval operation. The verb 'Get' and the nature of the request (fetching meeting information for a specific date) are consistent with read-only query functionality.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs tab_meetings 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_meetings, this is the rule to start with:
tab_meetings 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_meetings call is checked against it from then on.
Questions about tab_meetings
Get TAB race meetings for a date. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
tab_meetings accepts 3 parameters: date, api_key, jurisdiction. 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_meetings: 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_meetings 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_meetings 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_meetings. 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_meetings 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