This record as markdown: /tools/aiwerk-mcp-server-ghl/calendars-delete-event.md
What calendars_delete_event does on Ghl
AI agents call calendars_delete_event 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 |
|---|---|---|---|
body | object | Yes | Request body as defined by the HighLevel API. |
eventId | string | Yes | Event Id or Instance id. For recurring appointments send masterEventId to modify original series. |
Parameters from the server's own tool schema.
Why calendars_delete_event is rated Critical
An AI agent that decides to call calendars_delete_event doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Ghl is gone. There is no undo for destructive operations.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs calendars_delete_event 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 calendars_delete_event, this is the rule to start with:
calendars_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 Ghl, apply this rule, and every calendars_delete_event call is checked against it from then on.
Questions about calendars_delete_event
Delete Event. 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.
calendars_delete_event accepts 2 parameters: body, eventId. Required: body, eventId. 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 calendars_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 Ghl. Nothing to install.
calendars_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 calendars_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 calendars_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.
calendars_delete_event is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). 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