AI agents use eventbrite_create_event to create or update resources in UnClick — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | |
api_key | string | — | |
end_utc | string | Yes | |
currency | string | — | |
timezone | string | Yes | |
start_utc | string | Yes | |
organizer_id | string | — |
Parameters from the server's own tool schema.
This tool creates a new event, which is a reversible write operation. While event creation on a public platform could have downstream effects (tickets sold, attendees registered), the action itself is a standard Create operation that can be undone by deleting the event. It does not delete data (Destructive), move money (Financial), or execute arbitrary code (Execute).
From the tool's definition Tool name is 'eventbrite_create_event' and description states 'Create an event on Eventbrite.' The verb 'create' indicates data is being created/modified in the Eventbrite system.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
Create an event on Eventbrite. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
eventbrite_create_event accepts 7 parameters: name, api_key, end_utc, currency, timezone, start_utc, organizer_id. Required: name, end_utc, timezone, start_utc. 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_create_event: 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_create_event is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the eventbrite_create_event 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_create_event. 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_create_event 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →