[Calendar API v3] Delete a calendar event
Part of the Google Calendar and Meet server.
Free to start. No card required.
AI agents may call calendar_v3_delete_event to permanently remove or destroy resources in Google Calendar and Meet. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call calendar_v3_delete_event in a loop, permanently destroying resources in Google Calendar and Meet. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"calendar_v3_delete_event"
]
}See the full Google Calendar and Meet policy for all 25 tools.
These attack patterns abuse exactly the kind of access calendar_v3_delete_event gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
[Calendar API v3] Delete a calendar event. It is categorised as a Destructive tool in the Google Calendar and Meet MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Calendar and Meet MCP server in PolicyLayer and add a rule for calendar_v3_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 Calendar and Meet. Nothing to install.
calendar_v3_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_v3_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_v3_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_v3_delete_event is provided by the Google Calendar and Meet MCP server (INSIDE-HAIR/mcp-google-meet-and-calendar). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 25 Google Calendar and Meet tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.