tm_get_event
Get details for a specific Ticketmaster event.
This record as markdown: /tools/creativelead-unclick/tm-get-event.md
What tm_get_event does on UnClick
AI agents call tm_get_event 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 |
|---|---|---|---|
id | string | — | |
api_key | string | — |
Parameters from the server's own tool schema.
Why tm_get_event is rated Low
This tool retrieves publicly available event information from Ticketmaster. No data is modified, deleted, or created; no external actions are triggered; no financial transactions are involved. It is a simple data retrieval operation analogous to a search or fetch, fitting the 'Read' category with low severity and high confidence.
From the tool's definition Tool name 'tm_get_event' and description 'Get details for a specific Ticketmaster event' indicate a retrieval operation with the verb 'Get' which implies querying/fetching data without modification or side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs tm_get_event 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 tm_get_event, this is the rule to start with:
tm_get_event 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 tm_get_event call is checked against it from then on.
Questions about tm_get_event
Get details for a specific Ticketmaster event. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
tm_get_event accepts 2 parameters: id, api_key. 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 tm_get_event: 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.
tm_get_event 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 tm_get_event 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 tm_get_event. 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.
tm_get_event 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