delete_calendar
Delete a calendar from GoHighLevel
This record as markdown: /tools/hridayshah7-gohighlevel-mcp/delete-calendar.md
What delete_calendar does on GoHighLevel MCP Server
AI agents call delete_calendar to permanently remove resources in GoHighLevel MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_calendar is rated Critical
Deleting a calendar is an irreversible action that cannot be undone. This removes scheduling data and associated events, representing a destructive operation with significant blast radius in a business context where calendars are critical for team coordination and appointment management. The tool permits no recovery mechanism and directly aligns with the Destructive category definition.
From the tool's definition The tool name 'delete_calendar' combined with the description 'Delete a calendar from GoHighLevel' indicates permanent removal of a calendar object and its associated data.
Attacks that exploit this kind of access
The rule that runs delete_calendar safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GoHighLevel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_calendar, this is the rule to start with:
delete_calendar 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 GoHighLevel MCP Server, apply this rule, and every delete_calendar call is checked against it from then on.
Questions about delete_calendar
Delete a calendar from GoHighLevel. It is categorised as a Destructive tool in the GoHighLevel MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for delete_calendar: 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 GoHighLevel MCP Server. Nothing to install.
delete_calendar 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 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. 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 is provided by the GoHighLevel MCP Server MCP server (hridayshah7/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GoHighLevel MCP Server, and thousands of servers like it.
Across the catalogue