This record as markdown: /tools/ghl/delete-calendar-notification.md
What delete_calendar_notification does on Ghl
AI agents call delete_calendar_notification to permanently remove resources in Ghl, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
calendarId | string | Yes | Calendar ID |
notificationId | string | Yes | Notification ID |
Parameters from the server's own tool schema.
Why delete_calendar_notification is rated Critical
This tool permanently removes a calendar notification, which cannot be undone. While the impact is localized to a single notification (not a mass deletion), it is still a destructive action. Severity is medium rather than high because calendar notifications are typically low-criticality data compared to core business records or financial data.
From the tool's definition Tool name is 'delete_calendar_notification' with description 'Delete calendar notification'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete_calendar_notification safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_calendar_notification, this is the rule to start with:
delete_calendar_notification 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 Ghl, apply this rule, and every delete_calendar_notification call is checked against it from then on.
Questions about delete_calendar_notification
delete_calendar_notification is a destructive tool on the Ghl MCP server. It is categorised as a Destructive tool in the Ghl MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_calendar_notification accepts 2 parameters: calendarId, notificationId. Required: calendarId, notificationId. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for delete_calendar_notification: 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 Ghl. Nothing to install.
delete_calendar_notification 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 delete_calendar_notification 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 delete_calendar_notification. 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.
delete_calendar_notification is provided by the Ghl MCP server (ghl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
Across the catalogue