Governed ability
Get ticket
aafm/tec-get-ticketRead only
Get ticket is a governed Event Tickets ability in Agent Abilities for MCP, a free WordPress plugin that runs an MCP server on your site.
Read a single ticket by ID. Requires edit access to its parent event.
How it is governed
The same model as every ability in the plugin, stated for this one.
- Off until you enable it
Like every ability, Get ticket ships switched off. You turn it on one at a time, and an update never widens access on its own.
- Reads only
It reads data and returns it to your client. Nothing on your site is created, changed, or removed.
- Capability gated
A connection only sees Get ticket if the user you connected can run it, and the plugin checks that capability again before it executes.
- Every call audited
The call is written to the log in your own database, denials included, with the argument keys and the identifiers it touched, never free-text content.
Get ticket is one of the 3 governed Event Tickets abilities. See the full Event Tickets MCP integration.
See it in action
An illustrative run. Your real calls and data stay on your own site.
Try it with a prompt
Example requests you could paste to your agent.
Read ticket 88 and show me its price and capacity.
What are the details on this single ticket type?
Pull ticket 41 so I can check it against the event page.
These are illustrative example prompts. The agent runs them as the user you connected, checked against that user's capabilities and written to your audit log.
Frequently asked
Short answers for Get ticket.
Is this a write?
No. Get ticket reads one ticket by ID and changes nothing. No ticket purchase or issuance write exists in the plugin.
Who can read it?
Anyone with edit access to the ticket's parent event. The ability is off by default and every read is written to the audit log.
What does it need installed?
The Events Calendar 6.17.3.1 or newer and Event Tickets 5.29.3.1 or newer, both active.
Governed by default, from the first call.
Get ticket is off until you enable it, scoped to the user you connect, and logged like everything else. Turn on only what you need.
Every ability off until you enable it, capability-gated on every call.