Governed ability

Get attendees

aafm/tec-get-attendeesRead only

Get attendees is a governed Event Tickets ability in Agent Abilities for MCP, a free WordPress plugin that runs an MCP server on your site.

List attendees/RSVPs for one event, across every provider. Requires edit access to that 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 attendees 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 attendees 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 attendees 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.

agent-abilities · auditGoverned
YouGet attendees on this site.
RunRunning aafm/tec-get-attendees
GateAllowedread capability confirmed
Auditaafm/tec-get-attendees · principal: editor · args: event_id, ticket_id
ResultReturns the data the agent asked for. Nothing on the site changes.

Try it with a prompt

Example requests you could paste to your agent.

  1. How many attendees are registered for event 512?
  2. Check whether the RSVP list for this event has reached capacity.
  3. Look up attendee 88 on event 512 so I can confirm the booking.

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 attendees.

Is attendee data sensitive?

Yes. Attendees are real people and the list holds personal data, so treat the output accordingly. Keep requests narrow, to a specific event or a specific check, rather than pulling contact details in bulk.

Who can see it?

Only a caller with edit access to that event, and only after an administrator has enabled the ability. Every read is written to the audit log with the acting user.

Can it change a registration?

No. Get attendees lists attendees and RSVPs across every provider, and that is all. The Event Tickets abilities are read only.

Back to all abilities

Governed by default, from the first call.

Get attendees 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.