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

delete-event

Remove event from calendar. Returns: empty on success. Use when: canceling appointments. Note: permanent deletion, not recoverable.

SERVERMCP Google Workspace SOURCE199-mcp/mcp-google
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/199-biotechnologies-mcp-google/delete-event.md

What delete-event does on MCP Google Workspace

AI agents call delete-event to permanently remove resources in MCP Google Workspace, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete-event is rated Critical

This tool irreversibly deletes calendar events with no undo capability. While the blast radius is limited to calendar data (not financial or system-wide), the permanent nature of deletion and potential to disrupt appointments/schedules places it in the Destructive category.

From the tool's definition Tool description explicitly states "permanent deletion, not recoverable" and the name "delete-event" indicates irreversible removal of calendar data.

Questions about delete-event

What does the delete-event tool do? +

Remove event from calendar. Returns: empty on success. Use when: canceling appointments. Note: permanent deletion, not recoverable. It is categorised as a Destructive tool in the MCP Google Workspace 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-event? +

Register the MCP Google Workspace MCP server in PolicyLayer and add a rule for 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 MCP Google Workspace. Nothing to install.

What risk level is delete-event? +

delete-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-event? +

Yes. Add a rate_limit block to the 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.

How do I block delete-event completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides delete-event? +

delete-event is provided by the MCP Google Workspace MCP server (199-mcp/mcp-google). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on MCP Google Workspace, 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 MCP Google Workspace'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.