Delete a calendar event
AI agents call calendar_delete to permanently remove resources in Mailgent 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 and permanently removes scheduling information. While the blast radius is somewhat limited (affects only calendar data, not financial transactions or critical system integrity), the irreversibility and loss of data justify the Destructive category and high severity. Confidence is high because the intent is explicit in both name and description.
From the tool's definition Tool name is 'calendar_delete' with description 'Delete a calendar event' — the word '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 Mailgent MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mailgent MCP Server MCP server in PolicyLayer and add a rule for calendar_delete: 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 Mailgent MCP Server. Nothing to install.
calendar_delete 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 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. 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 is provided by the Mailgent MCP Server MCP server (loomal-ai/loomal-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 →