Use this when the user has given explicit written confirmation for a locked ticket quote and the agent should either execute an integrated provider purchase or return the required external checkout handoff.
AI agents use purchase_ticket_order to commit financial operations through Events — usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
quote_token | string | Yes | Opaque quote token returned by quote_ticket_order. |
idempotency_key | string | — | Optional idempotency key for integrated purchase providers. |
confirmation_text | string | Yes | User's explicit written confirmation, including buy/purchase, quantity, and max_total when present. |
user_payment_profile_id | string | — | Provider-specific saved payment profile id, when an integrated provider supports autonomous purchase. |
Parameters from the server's own tool schema.
This tool moves money by executing a ticket purchase on behalf of the user. Even though it requires explicit confirmation, it directly commits a financial obligation (ticket purchase) either through an integrated payment provider or by handing off to an external checkout. This squarely falls in the Financial category, which is the most severe applicable category.
From the tool's definition "execute an integrated provider purchase" and "locked ticket quote" — the tool directly processes a financial transaction to purchase tickets
Attacks that exploit this kind of access
Use this when the user has given explicit written confirmation for a locked ticket quote and the agent should either execute an integrated provider purchase or return the required external checkout handoff. It is categorised as a Financial tool in the Events MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
purchase_ticket_order accepts 4 parameters: quote_token, idempotency_key, confirmation_text, user_payment_profile_id. Required: quote_token, confirmation_text. 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 purchase_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.
purchase_ticket_order is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the purchase_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 purchase_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.
purchase_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.
purchase_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 →