createCalendarEvent
Create a new calendar event. Supports timed events, all-day events, and Google Meet integration.
This record as markdown: /tools/ark7-google-drive-mcp/createcalendarevent.md
What createCalendarEvent does on Google Drive
AI agents use createCalendarEvent to create or update resources in Google Drive, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Drive environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
end | object | Yes | End time |
start | object | Yes | Start time (use dateTime for timed events, date for all-day) |
account | string | — | Alias of the Google account to target. Optional — defaults to the session/global default account, or the sole authenticated account. Run manage_accounts list to |
summary | string | Yes | Event title |
location | string | — | Event location |
attendees | array | — | Email addresses of attendees |
calendarId | string | — | Calendar ID (default: primary) |
recurrence | array | — | RRULE strings for recurring events |
visibility | string | — | Event visibility |
attachments | array | — | File attachments (max 25). For Drive files use the file's share URL as fileUrl. |
description | string | — | Event description |
sendUpdates | string | — | Send notifications (default: none) |
Parameters from the server's own tool schema.
Why createCalendarEvent is rated Medium
This tool creates new calendar events, which is a reversible Write operation. It modifies calendar state by adding entries but does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or trigger uncontrolled external operations (Execute).
From the tool's definition Tool description states 'Create a new calendar event', which is a create operation that adds new data to Google Calendar.
Risk signalsHigh parameter count (22 properties)
Attacks that exploit this kind of access
The rule that runs createCalendarEvent safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Drive, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For createCalendarEvent, this is the rule to start with:
createCalendarEvent 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 Drive, apply this rule, and every createCalendarEvent call is checked against it from then on.
Questions about createCalendarEvent
Create a new calendar event. Supports timed events, all-day events, and Google Meet integration. It is categorised as a Write tool in the Google Drive MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
createCalendarEvent accepts 12 parameters: end, start, account, summary, location, attendees, calendarId, recurrence, visibility, attachments, description, sendUpdates. Required: end, start, summary. The full parameter table on this page comes from the server's own tool schema.
Register the Google Drive MCP server in PolicyLayer and add a rule for createCalendarEvent: 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 Drive. Nothing to install.
createCalendarEvent 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 createCalendarEvent 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 createCalendarEvent. 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.
createCalendarEvent is provided by the Google Drive MCP server (@ark7/google-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Drive, and thousands of servers like it.
This server
Across the catalogue