Critical-risk tools in Google Calendar
4 of the 29 tools in Google Calendar are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
GOOGLECALENDAR_CALENDARS_DELETEDestructive 4/5Deletes a secondary calendar. Use calendars.clear for clearing all events on primary calendars.
-
GOOGLECALENDAR_CLEAR_CALENDARDestructive 4/5Clears a primary calendar. This operation deletes all events associated with the primary calendar of an account.
-
GOOGLECALENDAR_DELETE_EVENTDestructive 4/5Deletes a specified event by `event_id` from a Google Calendar (`calendar_id`); this action is idempotent and raises a 404 error if the event is not found.
-
GOOGLECALENDAR_REMOVE_ATTENDEEDestructive 4/5Removes an attendee from a specified event in a Google Calendar; the calendar and event must exist.
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.
More on Google Calendar
Enforce policy on Google Calendar
One command generates a policy scaffold for every server in your MCP config.
npx -y @policylayer/intercept init