google_calendar_delete_events

Permanently delete an event from the primary calendar using its unique event ID.

Server ContextCore MCP rkpraveendev/contextcore-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What google_calendar_delete_events does on ContextCore MCP

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

Why google_calendar_delete_events needs a policy

Calendar events are user data that, once deleted permanently, cannot be restored. This action is irreversible and destructive. Although the blast radius is narrower than system-wide data deletion, the permanent nature and user-facing impact classify this as Destructive rather than Write.

From the tool's definition Tool description explicitly states "Permanently delete an event" — the use of "Permanently" indicates irreversible data loss. The tool accepts an event ID and removes calendar data that cannot be recovered through normal means.

Questions about google_calendar_delete_events

What does the google_calendar_delete_events tool do? +

Permanently delete an event from the primary calendar using its unique event ID. It is categorised as a Destructive tool in the ContextCore MCP 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 google_calendar_delete_events? +

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

What risk level is google_calendar_delete_events? +

google_calendar_delete_events 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 google_calendar_delete_events? +

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

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

google_calendar_delete_events is provided by the ContextCore MCP server (rkpraveendev/contextcore-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.