delete-integration
API to delete an association for an app and location
This record as markdown: /tools/drausal-gohighlevel-mcp/delete-integration.md
What delete-integration does on GoHighLevel MCP Server
AI agents call delete-integration 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 delete-integration is rated Critical
This tool performs an irreversible deletion operation that cannot be undone without manual reconfiguration. While it does not delete core business data like contacts or opportunities, deleting an integration association breaks the connection between an app and location, potentially disrupting business workflows and communications.
From the tool's definition The tool name explicitly contains 'delete' and the description states it 'delete[s] an association for an app and location', indicating irreversible removal of integration configuration data.
Attacks that exploit this kind of access
The rule that runs delete-integration safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GoHighLevel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete-integration, this is the rule to start with:
delete-integration 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 GoHighLevel MCP Server, apply this rule, and every delete-integration call is checked against it from then on.
Questions about delete-integration
API to delete an association for an app and location. 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.
Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for delete-integration: 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.
delete-integration 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-integration 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-integration. 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-integration 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.
More on GoHighLevel MCP Server, and thousands of servers like it.
Across the catalogue