delete_calendar

Delete a calendar from GoHighLevel

SERVERGoHighLevel MCP Server SOURCEbusybee3333/go-high-level-mcp-2026-complete
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/busybee3333-go-high-level-mcp-2026-complete/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

The 'delete_calendar' tool performs an irreversible deletion operation that removes a calendar object and its contents from the GoHighLevel CRM system. This cannot be undone and represents permanent data loss. While not a direct financial impact, deletion of calendars in a CRM system affects business operations (appointment history, scheduling records) and warrants Destructive classification.

From the tool's definition Tool name contains 'delete' and description states 'Delete a calendar from GoHighLevel' - irreversible removal of calendar data and associated scheduling information.

Questions about delete_calendar

What does the delete_calendar tool do? +

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.

How do I enforce a policy on delete_calendar? +

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.

What risk level is delete_calendar? +

delete_calendar is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_calendar? +

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.

How do I block delete_calendar completely? +

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.

What MCP server provides delete_calendar? +

delete_calendar is provided by the GoHighLevel MCP Server MCP server (busybee3333/go-high-level-mcp-2026-complete). 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GoHighLevel MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.