AI agents call calendar_deleteEvent to permanently remove resources in Google MCP Remote — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of calendar events cannot be undone and permanently removes user data. This is a destructive operation with potential business impact (missed meetings, lost scheduling information). High severity due to the irreversibility and potential for disruption if an AI agent deletes critical events without authorization. Confidence is high because the intent is unambiguous.
From the tool's definition Tool name explicitly states 'deleteEvent' and description confirms 'Delete a calendar event' — irreversible removal of calendar data.
Documented attack patterns abuse exactly the kind of access calendar_deleteEvent gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google MCP Remote, and nothing reaches the server without passing your rules. This is the rule we recommend for calendar_deleteEvent:
{
"version": "1",
"default": "deny",
"hide": [
"calendar_deleteEvent"
]
}calendar_deleteEvent disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a calendar event. It is categorised as a Destructive tool in the Google MCP Remote MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google MCP Remote MCP server in PolicyLayer and add a rule for calendar_deleteEvent: 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 Google MCP Remote. Nothing to install.
calendar_deleteEvent 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_deleteEvent 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_deleteEvent. 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_deleteEvent is provided by the Google MCP Remote MCP server (vakharwalad23/google-mcp-remote). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google MCP Remote, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
35 Google MCP Remote tools catalogued and risk-classified — across an index of 43,000+ MCP servers.