gcal_delete_event

Delete a calendar event.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-mcp

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/shriram-vasudevan-integrations-mcp/gcal-delete-event.md

WHAT IT DOES

What gcal_delete_event does on Integrations MCP

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

RISK

Why gcal_delete_event is rated Critical

Deleting a calendar event is an irreversible action that cannot be undone. Once deleted, the event is permanently removed from the user's Google Calendar unless restored from a backup. This fits the Destructive category (irreversibly deletes data).

From the tool's definition Tool name 'gcal_delete_event' and description 'Delete a calendar event' explicitly indicate permanent removal of calendar data with no recovery mechanism.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gcal_delete_event safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gcal_delete_event, this is the rule to start with:

gcal_delete_event Hidden

gcal_delete_event is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "gcal_delete_event"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every gcal_delete_event call is checked against it from then on.

FAQ

Questions about gcal_delete_event

What does the gcal_delete_event tool do? +

Delete a calendar event. It is categorised as a Destructive tool in the Integrations 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 gcal_delete_event? +

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

What risk level is gcal_delete_event? +

gcal_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 gcal_delete_event? +

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

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

gcal_delete_event is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Integrations, and thousands of servers like it.

This server

All 420 Integrations tools → Critical-risk tools on this server →

Across the catalogue

calendar_delete_event on Templonix Lite MCP Server →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →