calendar_delete_event
Delete an event from Google Calendar. This action cannot be undone. Use with caution.
This record as markdown: /tools/io-github-saloprj-dialogbrain/calendar-delete-event.md
What calendar_delete_event does on Dialogbrain
AI agents call calendar_delete_event to permanently remove resources in Dialogbrain, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
event_id | string | Yes | ID of the event to delete. Required. |
calendar_id | string | — | Calendar ID containing the event. OMIT to use the agent's configured default calendar (or primary). |
send_notifications | boolean | — | Whether to send cancellation notifications to attendees. |
Parameters from the server's own tool schema.
Why calendar_delete_event is rated Critical
An AI agent that decides to call calendar_delete_event doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Dialogbrain is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs calendar_delete_event safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For calendar_delete_event, this is the rule to start with:
calendar_delete_event is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every calendar_delete_event call is checked against it from then on.
Questions about calendar_delete_event
Delete an event from Google Calendar. This action cannot be undone. Use with caution. It is categorised as a Destructive tool in the Dialogbrain MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
calendar_delete_event accepts 3 parameters: event_id, calendar_id, send_notifications. Required: event_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for calendar_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 Dialogbrain. Nothing to install.
calendar_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 calendar_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 calendar_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.
calendar_delete_event is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
Across the catalogue