This record as markdown: /tools/googlesuper/googlesuper-calendars-update.md
What GOOGLESUPER_CALENDARS_UPDATE does on Google Super
AI agents use GOOGLESUPER_CALENDARS_UPDATE 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 | — | Title of the calendar. |
location | string | — | Geographic location of the calendar as free-form text. Optional. |
timeZone | string | — | The time zone of the calendar. (Formatted as an IANA Time Zone Database name, e.g. "Europe/Zurich".) Optional. |
calendarId | string | — | Calendar identifier. To retrieve calendar IDs call the calendarList.list method. If you want to access the primary calendar of the currently logged in user, use |
description | string | — | Description of the calendar. Optional. |
Parameters from the server's own tool schema.
Why GOOGLESUPER_CALENDARS_UPDATE is rated Medium
This tool modifies calendar metadata reversibly without deleting data or executing arbitrary code. It affects calendar configuration (name, description, timezone, etc.) but changes are non-destructive and can be undone.
From the tool's definition Tool name contains 'UPDATE' and description states 'Updates metadata for a calendar', indicating modification of existing calendar data.
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_CALENDARS_UPDATE 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_CALENDARS_UPDATE, this is the rule to start with:
GOOGLESUPER_CALENDARS_UPDATE 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_CALENDARS_UPDATE call is checked against it from then on.
Questions about GOOGLESUPER_CALENDARS_UPDATE
Updates metadata for a 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_CALENDARS_UPDATE accepts 5 parameters: summary, location, timeZone, calendarId, description. 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_CALENDARS_UPDATE: 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_CALENDARS_UPDATE 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_CALENDARS_UPDATE 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_CALENDARS_UPDATE. 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_CALENDARS_UPDATE 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