eventbrite_get_attendees
Get attendees for an Eventbrite event.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/eventbrite-get-attendees.md
What eventbrite_get_attendees does on UnClick
AI agents call eventbrite_get_attendees to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | — | |
event_id | string | Yes |
Parameters from the server's own tool schema.
Why eventbrite_get_attendees is rated Low
This tool retrieves attendee information from an Eventbrite event, which is a query operation that does not create, modify, delete, or execute code. It falls squarely into the Read category. Severity is low because retrieving attendee lists is a standard informational operation with minimal blast radius, though depending on data sensitivity and privacy regulations, confidence could vary slightly.
From the tool's definition Tool name 'eventbrite_get_attendees' and description 'Get attendees for an Eventbrite event' indicate data retrieval with no modification or side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs eventbrite_get_attendees safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For eventbrite_get_attendees, this is the rule to start with:
eventbrite_get_attendees is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every eventbrite_get_attendees call is checked against it from then on.
Questions about eventbrite_get_attendees
Get attendees for an Eventbrite event. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
eventbrite_get_attendees accepts 2 parameters: api_key, event_id. Required: event_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for eventbrite_get_attendees: 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 UnClick. Nothing to install.
eventbrite_get_attendees 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 eventbrite_get_attendees 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 eventbrite_get_attendees. 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.
eventbrite_get_attendees is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue