delete-calendar

Delete calendar by ID

SERVERGoHighLevel MCP Server SOURCEdrausal/gohighlevel-mcp

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/drausal-gohighlevel-mcp/delete-calendar.md

WHAT IT DOES

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.

RISK

Why delete-calendar is rated Critical

This tool permanently removes calendar records identified by ID with no undo capability. Deletion of calendars could disrupt scheduling, availability tracking, and business operations. While not financial, it represents irreversible data loss with significant business impact, making it Destructive rather than Write.

From the tool's definition delete-calendar with description 'Delete calendar by ID' performs irreversible deletion of calendar data

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Hidden

delete-calendar is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-calendar"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about delete-calendar

What does the delete-calendar tool do? +

Delete calendar by ID. 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 (drausal/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GoHighLevel MCP Server, and thousands of servers like it.

This server

All 406 GoHighLevel MCP Server tools → Critical-risk tools on this server →

Across the catalogue

calendar_delete_event on Templonix Lite MCP Server →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →