This record as markdown: /tools/ghl/ghl-delete-relation.md
What ghl_delete_relation does on Ghl
AI agents call ghl_delete_relation 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 | — | GoHighLevel location ID (will use default if not provided) |
relationId | string | Yes | The ID of the relation to delete |
Parameters from the server's own tool schema.
Why ghl_delete_relation is rated Critical
The tool performs an irreversible deletion action ('Delete a specific relation'). Even though it deletes a relationship rather than an entire entity, deletion operations that cannot be undone fall under the Destructive category.
From the tool's definition Tool name contains 'delete' and description states 'Delete a specific relation between two entities.' This is an irreversible deletion operation.
Attacks that exploit this kind of access
The rule that runs ghl_delete_relation 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 ghl_delete_relation, this is the rule to start with:
ghl_delete_relation 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 ghl_delete_relation call is checked against it from then on.
Questions about ghl_delete_relation
Delete a specific relation between two entities. 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.
ghl_delete_relation accepts 2 parameters: locationId, relationId. Required: relationId. 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 ghl_delete_relation: 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.
ghl_delete_relation 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 ghl_delete_relation 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 ghl_delete_relation. 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.
ghl_delete_relation 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