GOOGLESUPER_PATCH_EVENT
Update specified fields of an existing event in a Google Calendar using patch semantics (array fields like attendees are fully replaced if provided); ensure the calendar_id and event_id are valid and the user has write access to the calendar.
This record as markdown: /tools/googlesuper/googlesuper-patch-event.md
What GOOGLESUPER_PATCH_EVENT does on Google Super
AI agents use GOOGLESUPER_PATCH_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 | — | New title for the event. |
end_time | string | — | New end time (RFC3339 timestamp, e.g., '2024-07-01T11:00:00-07:00'). Uses `timezone` if provided, otherwise UTC. For all-day events, use YYYY-MM-DD format (excl |
event_id | string | — | Identifier of the event to update. Must be provided in snake_case format. |
location | string | — | New geographic location (physical address or virtual meeting link). |
timezone | string | — | IANA Time Zone Database name for start/end times (e.g., 'America/Los_Angeles'). Used if `start_time` and `end_time` are provided and not all-day dates; defaults |
attendees | array | — | List of email addresses for attendees. Replaces existing attendees. Provide an empty list to remove all. |
start_time | string | — | New start time (RFC3339 timestamp, e.g., '2024-07-01T10:00:00-07:00'). Uses `timezone` if provided, otherwise UTC. For all-day events, use YYYY-MM-DD format. |
calendar_id | string | — | Identifier of the calendar. Use 'primary' for the primary calendar of the logged-in user. To find other calendar IDs, use the `calendarList.list` method. Must b |
description | string | — | New description for the event; can include HTML. |
send_updates | string | — | Whether to send update notifications to attendees: 'all', 'externalOnly', or 'none'. Uses default user behavior if unspecified. |
max_attendees | integer | — | Maximum attendees in response; does not affect invited count. If more, response includes organizer only. Must be positive. |
rsvp_response | string | — | RSVP response status for the authenticated user. Updates only the current user's response status without affecting other attendees. Possible values: 'needsActio |
Parameters from the server's own tool schema.
Why GOOGLESUPER_PATCH_EVENT is rated Medium
This tool modifies existing calendar events by updating their fields. It is a Write operation because it changes data reversibly—events can be further modified or restored. It does not delete events (which would be Destructive), nor execute arbitrary code (Execute), nor move money (Financial).
From the tool's definition Update specified fields of an existing event in a Google Calendar using patch semantics; ensure the user has write access to the calendar.
Risk signalsHigh parameter count (14 properties)
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_PATCH_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_PATCH_EVENT, this is the rule to start with:
GOOGLESUPER_PATCH_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_PATCH_EVENT call is checked against it from then on.
Questions about GOOGLESUPER_PATCH_EVENT
Update specified fields of an existing event in a Google Calendar using patch semantics (array fields like attendees are fully replaced if provided); ensure the calendar_id and event_id are valid and the user has write access to the calendar. 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_PATCH_EVENT accepts 12 parameters: summary, end_time, event_id, location, timezone, attendees, start_time, calendar_id, description, send_updates, max_attendees, rsvp_response. 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_PATCH_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_PATCH_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_PATCH_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_PATCH_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_PATCH_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