GOOGLESUPER_CREATE_EVENT
Create a Google Calendar event using start_datetime plus event_duration_hour and event_duration_minutes fields to derive the end time. Requires calendar write access. The organizer is added as an attendee unless exclude_organizer is True. Example request to create event for 1 hour 30 minutes: { "...
This record as markdown: /tools/googlesuper/googlesuper-create-event.md
What GOOGLESUPER_CREATE_EVENT does on Google Super
AI agents use GOOGLESUPER_CREATE_EVENT to create or update resources in Google Super, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Super environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
summary | string | — | Summary (title) of the event. |
location | string | — | Geographic location of the event as free-form text. |
timezone | string | — | IANA timezone name (e.g., 'America/New_York'). Required if datetime is naive. For recurring events, start and end must include a timeZone. If not provided, UTC |
attendees | array | — | List of attendee emails (strings). |
eventType | string | — | Type of the event, immutable post-creation. 'workingLocation' (REQUIRES Google Workspace Enterprise). Note: 'fromGmail' events cannot be created via API. |
recurrence | array | — | List of RRULE, EXRULE, RDATE, EXDATE lines for recurring events. Supported frequencies: DAILY, WEEKLY, MONTHLY, YEARLY. For recurring events, start.timeZone and |
visibility | string | — | Event visibility: 'default', 'public', 'private', or 'confidential'. |
calendar_id | string | — | Target calendar: 'primary' for the user's main calendar, or the calendar's email address. Must be provided in snake_case format. |
description | string | — | Description of the event. Can contain HTML. Optional. Must be omitted for 'birthday' event type. |
send_updates | boolean | — | Defaults to True. Whether to send updates to the attendees. |
transparency | string | — | 'opaque' (busy) or 'transparent' (available). |
start_datetime | string | — | Event start time in format YYYY-MM-DDTHH:MM:SS (no fractional seconds, no 'Z', no timezone offsets). Examples: '2025-01-16T13:00:00' or '2025-01-16T13:00'. Time |
Parameters from the server's own tool schema.
Why GOOGLESUPER_CREATE_EVENT is rated Medium
This tool creates new calendar events, which is a reversible write operation. An AI agent could misuse it by scheduling unwanted meetings, flooding a calendar with spam events, or creating fake meeting invitations, causing disruption to the user's schedule and potentially affecting business operations. However, events can be deleted or modified, so it is not destructive.
From the tool's definition Tool description states it creates a Google Calendar event and requires 'calendar write access.' The verb 'create' combined with 'write access' confirms this modifies data.
Risk signalsHigh parameter count (41 properties)
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_CREATE_EVENT safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Super, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For GOOGLESUPER_CREATE_EVENT, this is the rule to start with:
GOOGLESUPER_CREATE_EVENT stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Google Super, apply this rule, and every GOOGLESUPER_CREATE_EVENT call is checked against it from then on.
Questions about GOOGLESUPER_CREATE_EVENT
Create a Google Calendar event using start_datetime plus event_duration_hour and event_duration_minutes fields to derive the end time. Requires calendar write access. The organizer is added as an attendee unless exclude_organizer is True. Example request to create event for 1 hour 30 minutes: { "calendar_id": "primary", "start_datetime": "2025-01-16T13:00:00", "timezone": "America/New_York", "event_duration_hour": 1, "event_duration_minutes": 30, "summary": "Client sync", "attendees": [{"email": "guest@example.com"}] }. It is categorised as a Write tool in the Google Super MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
GOOGLESUPER_CREATE_EVENT accepts 12 parameters: summary, location, timezone, attendees, eventType, recurrence, visibility, calendar_id, description, send_updates, transparency, start_datetime. The full parameter table on this page comes from the server's own tool schema.
Register the Google Super MCP server in PolicyLayer and add a rule for GOOGLESUPER_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 Google Super. Nothing to install.
GOOGLESUPER_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 GOOGLESUPER_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 GOOGLESUPER_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.
GOOGLESUPER_CREATE_EVENT is provided by the Google Super MCP server (googlesuper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Super, and thousands of servers like it.
This server
Across the catalogue