Delete a calendar event
AI agents call delete_calendar_event to permanently remove resources in Google Workspace 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 cannot be undone without manual recovery or restore operations. This is an irreversible action that modifies or removes user data. While the blast radius is limited to a single calendar entry (not system-wide data), deletion is categorically destructive.
From the tool's definition The tool is named 'delete_calendar_event' and its description states it will 'Delete a calendar event'. The verb 'delete' is explicitly destructive—the action removes data irreversibly.
Attacks that exploit this kind of access
Delete a calendar event. It is categorised as a Destructive tool in the Google Workspace MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Workspace MCP Server MCP server in PolicyLayer and add a rule for delete_calendar_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 Workspace MCP Server. Nothing to install.
delete_calendar_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 delete_calendar_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 delete_calendar_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.
delete_calendar_event is provided by the Google Workspace MCP Server MCP server (pbulbule13/google-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 →