Delete a calendar event
AI agents call delete_calendar_event to permanently remove resources in Enhanced MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes calendar event data, which cannot be undone. Deletion is an irreversible operation that destroys data. While the blast radius is limited to calendar events (not financial or system-critical), an AI agent misusing this tool could erase important meetings, appointments, or scheduling information. This warrants 'high' severity and the 'Destructive' category per the classification rules.
From the tool's definition Tool name is 'delete_calendar_event' with description 'Delete a calendar event'. The verb 'delete' 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 Enhanced MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Enhanced 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 Enhanced 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 Enhanced MCP Server MCP server (pbulbule13/mcpwithgoogle). 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 →