GOOGLESUPER_PATCH_CALENDAR

SERVERGoogle Super SOURCEgooglesuper

Medium RISK CLASS

Category Write

Parameters 50 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/googlesuper/googlesuper-patch-calendar.md

WHAT IT DOES

What GOOGLESUPER_PATCH_CALENDAR does on Google Super

AI agents use GOOGLESUPER_PATCH_CALENDAR 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 calendar; cannot be an empty string.
`location`	string	—	New geographic location of the calendar (e.g., 'Paris, France').
`timezone`	string	—	New IANA Time Zone Database name for the calendar (e.g., 'Europe/Zurich', 'America/New_York').
`calendar_id`	string	—	Identifier of the Google Calendar to update; use 'primary' for the main calendar or a specific ID.
`description`	string	—	New description for the calendar.

Parameters from the server's own tool schema.

RISK

Why GOOGLESUPER_PATCH_CALENDAR is rated Medium

This is a reversible modification of calendar data. It creates or updates calendar metadata without deleting data or triggering destructive operations. The blast radius is medium because misuse could alter calendar visibility, sharing, or informational properties that others rely on, but changes can be undone. Not Execute (no code/command execution) or Destructive (updates are reversible).

From the tool's definition Tool performs a PATCH operation to partially update calendar fields including summary, description, and location. Description explicitly states it 'modifies only the fields provided' and allows clearing fields with empty strings.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs GOOGLESUPER_PATCH_CALENDAR 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_CALENDAR, this is the rule to start with:

GOOGLESUPER_PATCH_CALENDAR Rate-limited

GOOGLESUPER_PATCH_CALENDAR 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "GOOGLESUPER_PATCH_CALENDAR": {
      "limits": [
        {
          "counter": "googlesuper_patch_calendar_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Google Super, apply this rule, and every GOOGLESUPER_PATCH_CALENDAR call is checked against it from then on.

FAQ

Questions about GOOGLESUPER_PATCH_CALENDAR

What does the GOOGLESUPER_PATCH_CALENDAR tool do? +

Partially updates (PATCHes) an existing Google Calendar, modifying only the fields provided; summary is mandatory and cannot be an empty string, and an empty string for description or location clears them. 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.

What parameters does GOOGLESUPER_PATCH_CALENDAR accept? +

GOOGLESUPER_PATCH_CALENDAR accepts 5 parameters: summary, location, timezone, calendar_id, description. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on GOOGLESUPER_PATCH_CALENDAR? +

Register the Google Super MCP server in PolicyLayer and add a rule for GOOGLESUPER_PATCH_CALENDAR: 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.

What risk level is GOOGLESUPER_PATCH_CALENDAR? +

GOOGLESUPER_PATCH_CALENDAR is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit GOOGLESUPER_PATCH_CALENDAR? +

Yes. Add a rate_limit block to the GOOGLESUPER_PATCH_CALENDAR 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.

How do I block GOOGLESUPER_PATCH_CALENDAR completely? +

Set action: deny in the PolicyLayer policy for GOOGLESUPER_PATCH_CALENDAR. 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.

What MCP server provides GOOGLESUPER_PATCH_CALENDAR? +

GOOGLESUPER_PATCH_CALENDAR 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.

KEEP EXPLORING

More on Google Super, and thousands of servers like it.

This server

All 200 Google Super tools →

Across the catalogue

calendar_create_event on Apple Apps MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →