AI agents call get_ticket_offers to retrieve information from Events without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
event_id | string | Yes | Event id returned by search, recommendations, plan_night, or get_event. |
Parameters from the server's own tool schema.
The tool retrieves (Read) ticket options/information for display purposes. It occurs before any purchase action ("before quoting or buying"), so it is purely informational with no side effects, no financial commitment, and no data modification. The word 'offers' and the pre-purchase context confirm this is a query/retrieval operation with minimal blast radius.
From the tool's definition Tool description states "Use this when a user wants ticket options for a specific UPlayground event before quoting or buying" - it retrieves ticket information without modifying data or executing transactions.
Attacks that exploit this kind of access
Use this when a user wants ticket options for a specific UPlayground event before quoting or buying. It is categorised as a Read tool in the Events MCP Server, which means it retrieves data without modifying state.
get_ticket_offers accepts 1 parameter: event_id. Required: event_id. The full parameter table on this page comes from the server's own tool schema.
Register the Events MCP server in PolicyLayer and add a rule for get_ticket_offers: 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 Events. Nothing to install.
get_ticket_offers 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 get_ticket_offers 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 get_ticket_offers. 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.
get_ticket_offers is provided by the Events MCP server (uplayground-events). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_ticket_offers is one line of Events's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →