This record as markdown: /tools/ghl/delete-location.md
What delete_location does on Ghl
AI agents call delete_location to permanently remove resources in Ghl, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
locationId | string | Yes | The unique ID of the location to delete |
deleteTwilioAccount | boolean | Yes | Whether to delete associated Twilio account |
Parameters from the server's own tool schema.
Why delete_location is rated Critical
Deletion of a location/sub-account is a destructive operation that cannot be undone. This action permanently removes infrastructure, associated data, and operational access. The blast radius is critical as it affects an entire business sub-unit and all its related data and users. This is the most severe action possible on this server.
From the tool's definition Tool name 'delete_location' and description 'Delete a sub-account/location from GoHighLevel' explicitly indicate irreversible deletion of an organizational entity (sub-account/location).
Attacks that exploit this kind of access
The rule that runs delete_location safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_location, this is the rule to start with:
delete_location 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 Ghl, apply this rule, and every delete_location call is checked against it from then on.
Questions about delete_location
Delete a sub-account/location from GoHighLevel. It is categorised as a Destructive tool in the Ghl MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_location accepts 2 parameters: locationId, deleteTwilioAccount. Required: locationId, deleteTwilioAccount. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl 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 Ghl. Nothing to install.
delete_location 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_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.
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.
delete_location is provided by the Ghl MCP server (ghl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
Across the catalogue