New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_calendar_event

Delete a calendar event. Requires TREKMAIL_ALLOW_DESTRUCTIVE=true.

SERVERTrekMail MCP Server SOURCEtrekmail/mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/trekmail-mcp-server/delete-calendar-event.md

What delete_calendar_event does on TrekMail MCP Server

AI agents call delete_calendar_event to permanently remove resources in TrekMail MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_calendar_event is rated Critical

This tool permanently removes calendar event data with no undo capability. The explicit destructive flag requirement confirms the developers recognize this as a high-risk operation. While calendar events may be less critical than financial data, deletion is irreversible and affects user operations/scheduling.

From the tool's definition Tool name is 'delete_calendar_event' and description explicitly states 'Delete a calendar event' with a requirement for TREKMAIL_ALLOW_DESTRUCTIVE=true flag, clearly indicating irreversible deletion.

Questions about delete_calendar_event

What does the delete_calendar_event tool do? +

Delete a calendar event. Requires TREKMAIL_ALLOW_DESTRUCTIVE=true. It is categorised as a Destructive tool in the TrekMail MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_calendar_event? +

Register the TrekMail 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 TrekMail MCP Server. Nothing to install.

What risk level is delete_calendar_event? +

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.

Can I rate-limit delete_calendar_event? +

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.

How do I block delete_calendar_event completely? +

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.

What MCP server provides delete_calendar_event? +

delete_calendar_event is provided by the TrekMail MCP Server MCP server (trekmail/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on TrekMail MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of TrekMail MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.