Delete a calendar event. Requires user confirmation before calling.
AI agents call cal_delete_event to permanently remove resources in Hermes Google — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion is an irreversible action that cannot be undone. Even though user confirmation is required before calling, the tool itself performs permanent removal of calendar events, making it a Destructive operation.
From the tool's definition Tool name is 'cal_delete_event' and description states 'Delete a calendar event' — this irreversibly removes calendar data.
Attacks that exploit this kind of access
Delete a calendar event. Requires user confirmation before calling. It is categorised as a Destructive tool in the Hermes Google MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hermes Google MCP server in PolicyLayer and add a rule for cal_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 Hermes Google. Nothing to install.
cal_delete_event 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 cal_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.
Set action: deny in the PolicyLayer policy for cal_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.
cal_delete_event is provided by the Hermes Google MCP server (jimmy-larsson/hermes-google). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →