tm_search_attractions
Search for attractions/artists on Ticketmaster.
This record as markdown: /tools/creativelead-unclick/tm-search-attractions.md
What tm_search_attractions does on UnClick
AI agents call tm_search_attractions 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 | — | |
keyword | string | — | |
classificationName | string | — |
Parameters from the server's own tool schema.
Why tm_search_attractions is rated Low
This tool performs a search query against Ticketmaster's attractions/artists database, retrieving publicly available information without side effects. It does not execute code, modify data, delete records, or commit financial transactions. The action is purely informational retrieval, fitting the Read category with low severity due to minimal risk if misused by an AI agent.
From the tool's definition Tool name 'tm_search_attractions' and description 'Search for attractions/artists on Ticketmaster' indicate a read-only query operation with no data modification or execution.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs tm_search_attractions 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_search_attractions, this is the rule to start with:
tm_search_attractions 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_search_attractions call is checked against it from then on.
Questions about tm_search_attractions
Search for attractions/artists on Ticketmaster. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
tm_search_attractions accepts 3 parameters: api_key, keyword, classificationName. 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_search_attractions: 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_search_attractions 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_search_attractions 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_search_attractions. 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_search_attractions 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