Update or delete calendar events by ID, name, or search criteria
AI agents call update_events to permanently remove resources in Google Calendar MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool combines Write (update) and Destructive (delete) operations. Per the rules, the most severe applicable category must be chosen, which is Destructive. The ability to delete events by broad search criteria amplifies the blast radius, as an AI agent could inadvertently delete multiple calendar events matching a query.
From the tool's definition 'Update or delete calendar events by ID, name, or search criteria' — explicitly includes deletion of events
Attacks that exploit this kind of access
Update or delete calendar events by ID, name, or search criteria. It is categorised as a Destructive tool in the Google Calendar MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Calendar MCP Server MCP server in PolicyLayer and add a rule for update_events: 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 Calendar MCP Server. Nothing to install.
update_events is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the update_events 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 update_events. 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.
update_events is provided by the Google Calendar MCP Server MCP server (kashyab19/google-calendar-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →