This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/tm-get-venue.md
What tm_get_venue does on UnClick
AI agents call tm_get_venue 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 | Yes | |
api_key | string | — |
Parameters from the server's own tool schema.
Why tm_get_venue is rated Low
This tool retrieves publicly available venue information from Ticketmaster without modifying, deleting, or executing any operations. It poses minimal security risk as it only queries and returns data with no side effects.
From the tool's definition Tool name 'tm_get_venue' and description 'Get details for a specific Ticketmaster venue' indicate a retrieval operation. The verb 'Get' and lack of any modification, deletion, or execution language confirms this is a read-only query.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs tm_get_venue 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_venue, this is the rule to start with:
tm_get_venue 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_venue call is checked against it from then on.
Questions about tm_get_venue
Get details for a specific Ticketmaster venue. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
tm_get_venue accepts 2 parameters: id, api_key. Required: id. 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_venue: 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_venue 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_venue 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_venue. 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_venue 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