This record as markdown: /tools/creativelead-unclick/tm-search-venues.md
What tm_search_venues does on UnClick
AI agents call tm_search_venues 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 | — | |
stateCode | string | — | |
countryCode | string | — |
Parameters from the server's own tool schema.
Why tm_search_venues is rated Low
This tool performs a query/search operation to retrieve venue information from Ticketmaster. It has no side effects, does not execute code or commands, does not modify data, and does not involve financial transactions. This is a straightforward Read category tool with low severity due to the benign nature of publicly searchable venue information.
From the tool's definition Tool name 'tm_search_venues' and description 'Search for venues on Ticketmaster' indicate a search operation that retrieves venue data without modifying, executing external processes, or creating financial transactions.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs tm_search_venues 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_venues, this is the rule to start with:
tm_search_venues 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_venues call is checked against it from then on.
Questions about tm_search_venues
Search for venues on Ticketmaster. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
tm_search_venues accepts 4 parameters: api_key, keyword, stateCode, countryCode. 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_venues: 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_venues 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_venues 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_venues. 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_venues 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