Critical Risk →

delete-location

Delete a Sub-Account (Formerly Location) from the Agency

How to control delete-location ↓

What delete-location does on GoHighLevel MCP Server

AI agents call delete-location 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.

Critical Risk

Why delete-location needs a policy

This tool performs an irreversible deletion operation on a sub-account/location, which cannot be undone. Deleting a location would likely cascade delete associated contacts, opportunities, calendars, workflows, and communications data. The blast radius is substantial as it affects an entire business unit.

From the tool's definition Tool name 'delete-location' combined with description 'Delete a Sub-Account (Formerly Location) from the Agency' explicitly indicates irreversible deletion of a business entity and all associated data.

Documented attack patterns abuse exactly the kind of access delete-location gives an agent:

How to control delete-location

PolicyLayer is an MCP gateway — it sits between your AI agents and GoHighLevel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-location:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-location"
  ]
}

delete-location disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register GoHighLevel MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete-location

What does the delete-location tool do? +

Delete a Sub-Account (Formerly Location) from the Agency. 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-location? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for delete-location: 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-location? +

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

Yes. Add a rate_limit block to the delete-location 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-location completely? +

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

delete-location 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.

Enforce policy on every GoHighLevel MCP Server tool call.

Start from GoHighLevel MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

406 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.