delete-event

Delete event 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-event.md

WHAT IT DOES

What delete-event does on GoHighLevel MCP Server

AI agents call delete-event 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-event is rated Critical

Deletion is an irreversible operation that cannot be undone. In a business context (GoHighLevel is a business management platform), deleting events can disrupt schedules, client communications, and business operations. This qualifies as Destructive rather than Execute because the primary effect is data destruction, not conditional execution.

From the tool's definition Tool name 'delete-event' and description 'Delete event by ID' directly indicate permanent deletion of calendar events.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete-event 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-event, this is the rule to start with:

delete-event Hidden

delete-event 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-event"
  ]
}

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-event call is checked against it from then on.

FAQ

Questions about delete-event

What does the delete-event tool do? +

Delete event 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-event? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for 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 GoHighLevel MCP Server. Nothing to install.

What risk level is delete-event? +

delete-event 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-event? +

Yes. Add a rate_limit block to the 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.

How do I block delete-event completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides delete-event? +

delete-event 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 →