updateCalendarEvent
Update an existing calendar event
This record as markdown: /tools/ark7-google-drive-mcp/updatecalendarevent.md
What updateCalendarEvent does on Google Drive
AI agents use updateCalendarEvent 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 | — | |
start | object | — | |
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 |
eventId | string | Yes | The event ID to update |
summary | string | — | New event title |
location | string | — | New event location |
attendees | array | — | Updated attendee emails (replaces existing) |
calendarId | string | — | Calendar ID (default: primary) |
attachments | array | — | File attachments (max 25). Replaces existing attachments; pass an empty array to remove all, or omit to keep them. For Drive files use the file's share URL as f |
description | string | — | New event description |
sendUpdates | string | — | Send notifications (default: none) |
Parameters from the server's own tool schema.
Why updateCalendarEvent is rated Medium
This tool modifies calendar event data but does not delete it or trigger external financial transactions. The operation is reversible (the previous state can be restored). While calendar events may have business implications, the tool itself only modifies metadata and scheduling information without committing financial obligations or triggering irreversible destructive actions.
From the tool's definition Tool name 'updateCalendarEvent' and description 'Update an existing calendar event' indicate modification of existing calendar data. The verb 'update' is characteristic of Write operations that create or modify data reversibly.
Risk signalsHigh parameter count (20 properties)
Attacks that exploit this kind of access
The rule that runs updateCalendarEvent 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 updateCalendarEvent, this is the rule to start with:
updateCalendarEvent 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 updateCalendarEvent call is checked against it from then on.
Questions about updateCalendarEvent
Update an existing calendar event. 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.
updateCalendarEvent accepts 11 parameters: end, start, account, eventId, summary, location, attendees, calendarId, attachments, description, sendUpdates. Required: eventId. 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 updateCalendarEvent: 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.
updateCalendarEvent 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 updateCalendarEvent 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 updateCalendarEvent. 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.
updateCalendarEvent 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