This record as markdown: /tools/creativelead-unclick/tm-search-events.md
What tm_search_events does on UnClick
AI agents call tm_search_events 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 |
|---|---|---|---|
city | string | — | |
size | number | — | |
api_key | string | — | |
keyword | string | — | |
countryCode | string | — | |
startDateTime | string | — | |
classificationName | string | — |
Parameters from the server's own tool schema.
Why tm_search_events is rated Low
This tool retrieves event information from Ticketmaster without modifying, creating, deleting, or executing any operations. It is a straightforward data retrieval function, which falls under the Read category. The blast radius of misuse is minimal—an agent could only retrieve publicly available event data.
From the tool's definition Tool name 'tm_search_events' and description 'Search for events on Ticketmaster' indicate a query/search operation with no side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs tm_search_events 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_events, this is the rule to start with:
tm_search_events 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_events call is checked against it from then on.
Questions about tm_search_events
Search for events on Ticketmaster. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
tm_search_events accepts 7 parameters: city, size, api_key, keyword, countryCode, startDateTime, 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_events: 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_events 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_events 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_events. 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_events 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