ghl_delete_association

Delete a user-defined association. This will also delete all relations created with this association.

Server GoHighLevel MCP Server mindflowedstudios/mindflowed_mcp
Category Destructive
Risk class Critical
Parameters 00 required

What ghl_delete_association does on GoHighLevel MCP Server

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

Why ghl_delete_association needs a policy

This tool performs an irreversible deletion operation that cannot be undone and has cascading side effects (deletes all relations tied to the association). In a CRM context, deleting associations could affect multiple business relationships and data integrity. This qualifies as Destructive rather than Execute because the primary action is permanent data removal, not conditional execution based on arguments.

From the tool's definition Tool description explicitly states "Delete a user-defined association" and "will also delete all relations created with this association". The use of "Delete" combined with cascading deletion of related data indicates irreversible removal.

Questions about ghl_delete_association

What does the ghl_delete_association tool do? +

Delete a user-defined association. This will also delete all relations created with this association. 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 ghl_delete_association? +

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

ghl_delete_association 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 ghl_delete_association? +

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

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

ghl_delete_association is provided by the GoHighLevel MCP Server MCP server (mindflowedstudios/mindflowed_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.