Delete a calendar event
AI agents call calendar-delete-event to permanently remove resources in Google Services MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a calendar event is a destructive operation that cannot be undone and removes data permanently from the user's calendar. This represents a higher severity than Write operations because the action is irreversible. While not as critical as financial transactions, the destructive nature and potential impact on user schedules (missed meetings, lost information) warrants a 'high' severity classification.
From the tool's definition Tool name is 'calendar-delete-event' with description 'Delete a calendar event'. The verb 'Delete' combined with operation on calendar events indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a calendar event. It is categorised as a Destructive tool in the Google Services MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Services MCP Server MCP server in PolicyLayer and add a rule for calendar-delete-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 Services MCP Server. Nothing to install.
calendar-delete-event 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 calendar-delete-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 calendar-delete-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.
calendar-delete-event is provided by the Google Services MCP Server MCP server (ricleedo/google-service-mcp). 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 →