ticketmaster.events.by_venue
Get upcoming events at a specific venue by venue ID (Ticketmaster)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ticketmaster.events.by-venue.md
What ticketmaster.events.by_venue does on Apibase
AI agents call ticketmaster.events.by_venue to retrieve information from Apibase 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 |
|---|---|---|---|
page | integer | — | Page number for pagination (0-based, default 0) |
size | integer | — | Number of results per page (1-200, default 20) |
sort | string | — | Sort order (e.g. "date,asc", "relevance,desc") |
locale | string | — | Locale for response (e.g. "en-us") |
keyword | string | — | Optional keyword filter for events at this venue |
venueId | string | Yes | Ticketmaster venue ID (e.g. "KovZpZA7AAEA" for Madison Square Garden) |
endDateTime | string | — | End date/time in ISO 8601 format with Z suffix |
startDateTime | string | — | Start date/time in ISO 8601 format with Z suffix |
Parameters from the server's own tool schema.
Why ticketmaster.events.by_venue is rated Low
Retrieves public event data; no side effects, modifications, or external actions triggered.
From the tool's definition Get upcoming events at a specific venue by venue ID
Attacks that exploit this kind of access
The rule that runs ticketmaster.events.by_venue safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ticketmaster.events.by_venue, this is the rule to start with:
ticketmaster.events.by_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 Apibase, apply this rule, and every ticketmaster.events.by_venue call is checked against it from then on.
Questions about ticketmaster.events.by_venue
Get upcoming events at a specific venue by venue ID (Ticketmaster). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
ticketmaster.events.by_venue accepts 8 parameters: page, size, sort, locale, keyword, venueId, endDateTime, startDateTime. Required: venueId. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for ticketmaster.events.by_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 Apibase. Nothing to install.
ticketmaster.events.by_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 ticketmaster.events.by_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 ticketmaster.events.by_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.
ticketmaster.events.by_venue is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue