ticketmaster.events.categories
Get all event classification categories — segments, genres, sub-genres (Ticketmaster)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ticketmaster.events.categories.md
What ticketmaster.events.categories does on Apibase
AI agents call ticketmaster.events.categories 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) |
locale | string | — | Locale for response (e.g. "en-us") |
Parameters from the server's own tool schema.
Why ticketmaster.events.categories is rated Low
Tool retrieves static event category data with no side effects, write capabilities, or external operations.
From the tool's definition Get all event classification categories — segments, genres, sub-genres
Attacks that exploit this kind of access
The rule that runs ticketmaster.events.categories 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.categories, this is the rule to start with:
ticketmaster.events.categories 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.categories call is checked against it from then on.
Questions about ticketmaster.events.categories
Get all event classification categories — segments, genres, sub-genres (Ticketmaster). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
ticketmaster.events.categories accepts 3 parameters: page, size, locale. 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.categories: 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.categories 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.categories 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.categories. 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.categories 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