New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

ghl_delete_relation

Delete a specific relation between two entities.

SERVERGoHighLevel MCP Server SOURCEmindflowedstudios/mindflowed_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/mindflowedstudios-mindflowed-mcp/ghl-delete-relation.md

What ghl_delete_relation does on GoHighLevel MCP Server

AI agents call ghl_delete_relation 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_relation is rated Critical

This tool performs irreversible deletion of relational data. While deletion of a single relation may have narrower blast radius than bulk operations, it still permanently removes data that cannot be recovered through the tool's normal interface. Classified as Destructive rather than Write because deletion cannot be undone.

From the tool's definition Tool name includes 'delete' and description states 'Delete a specific relation between two entities.' The action is irreversible data deletion.

Questions about ghl_delete_relation

What does the ghl_delete_relation tool do? +

Delete a specific relation between two entities. 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_relation? +

Register the GoHighLevel MCP Server 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 GoHighLevel MCP Server. Nothing to install.

What risk level is ghl_delete_relation? +

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.

Can I rate-limit ghl_delete_relation? +

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.

How do I block ghl_delete_relation completely? +

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.

What MCP server provides ghl_delete_relation? +

ghl_delete_relation 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.

More on GoHighLevel MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GoHighLevel MCP Server's. Pull the full record:

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.