Giving an AI assistant access to an account deserves care. This page describes what Eventa's MCP server exposes, what it never exposes, and the layers that keep it that way.
What an assistant can never get
| Never available | Why |
|---|---|
| Payments, orders, refunds, payouts, balances | There is no permission for money. Purchases finish on eventa.live |
| Password, email address, phone number, account deletion | Account settings are closed to connected apps |
| Email addresses and phone numbers of other people | Guests appear by name only, even to hosts |
| Ticket QR codes and scan history | A ticket is opened on eventa.live or in the Eventa app |
| Answers to registration forms | They stay with the host in the website |
| Private messages and posting | Not offered |
| A search for people | Public search returns events and clubs, never users |
Layers of protection
Permissions you approve. An app asks for specific permissions and you see each one in plain words before allowing it. You can disconnect it at any time in Settings → Connected apps; the connection stops working within about a minute.
Tokens only for this server. An access token is issued for https://mcp.eventa.live/mcp and the server rejects tokens meant for anything else. It never passes your token on to another service: for its own calls it exchanges the token for a separate short-lived one.
A closed list of allowed actions. The Eventa API keeps a list of the exact routes a connected app may use, each with the permission it needs. A route that is not on the list answers 403, whatever permissions the token has. New features are therefore invisible to connected apps until someone decides otherwise.
The same rules as the website. The API checks your role on each event and club. A host tool works only for events you run. An assistant cannot reach more than you could.
Allow-lists for what comes back. Results are built from named fields only. A field added to the API later does not appear in tool output by accident.
Two steps for anything that reaches other people. Approving or rejecting RSVPs and emailing invitations first return a preview. They carry out the action only when the request is repeated with a confirmation token. The token is bound to your account, the action and the exact guests or addresses previewed, and it expires after 10 minutes. Clients show their own approval prompt as well.
Bounded actions.
| Action | Bound |
|---|---|
| Changes through assistants | 30 per account in any 10 minutes |
| RSVP decisions | Up to 10 per request, only for RSVPs that are still waiting on that event |
| Invitations | Up to 10 addresses per request, and only for published events |
| Promo codes | Percentage up to 90, a usage limit of at most 1,000, ending within a year |
Text written by other people
Event descriptions, club names, reviews and guest notes are written by users. They could contain instructions aimed at an AI. Eventa labels such text as organizer_content, truncates it, and tells assistants in the tool descriptions to treat it as information and never as instructions. Anything that changes data also requires a request from you and, for bulk actions, the two-step confirmation.
Client authors should keep a human approval step for any tool that changes data, and should not let content from tool results trigger other tool calls without it.
Data handling
- The MCP server stores nothing about you. It is stateless: it forwards each request and keeps no sessions or copies of results.
- The Eventa API stores a record of each connection: which app, which permissions, when it was approved and last used. It stores refresh tokens only in hashed form. You see this record in Connected apps, and it is removed or ended when you disconnect.
- Tokens, authorization headers and service keys are removed from logs. Requests are logged with the tool name, duration and outcome.
- All traffic uses HTTPS.
Reporting a problem
If you find a security issue, do not post it publicly. Contact Eventa through Contact support or email [email protected], and describe what you found. Never include tokens or other people's personal data in a report.