AI agents call quote_ticket_order 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 |
|---|---|---|---|
currency | string | — | Preferred currency for max_total, for example USD. |
event_id | string | Yes | Event id returned by search, recommendations, plan_night, or get_event. |
offer_id | string | — | Optional offer_id returned by get_ticket_offers. |
quantity | number | — | |
max_total | number | — | Maximum all-in total the user authorizes before the agent must stop and ask again. |
ticket_type | string | — | Requested ticket type, for example GA, balcony, seated, VIP, or best available. |
refund_terms | string | — | Minimum refund/transfer terms the user accepts. |
Parameters from the server's own tool schema.
This tool queries and returns ticket pricing and availability information. It explicitly stops short of actual purchase—no money moves, no order is created, and no data is modified. It is a read-only retrieval of a quote/estimate. Even though tickets are involved, the tool does not execute the purchase (Write) or charge (Financial); it only presents terms for the user to review before deciding to proceed.
From the tool's definition Tool provides a 'locked ticket quote' with 'quantity, max price, ticket type, and stop conditions before any purchase attempt.' The word 'quote' and 'before any purchase attempt' indicate this retrieves pricing information without committing to a transaction…
Attacks that exploit this kind of access
Use this when a user has chosen an event and wants a locked ticket quote with quantity, max price, ticket type, and stop conditions before any purchase attempt. It is categorised as a Read tool in the Events MCP Server, which means it retrieves data without modifying state.
quote_ticket_order accepts 7 parameters: currency, event_id, offer_id, quantity, max_total, ticket_type, refund_terms. 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 quote_ticket_order: 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.
quote_ticket_order 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 quote_ticket_order 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 quote_ticket_order. 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.
quote_ticket_order 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.
quote_ticket_order 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 →