disconnect_integration

Disconnect a third-party integration

SERVERGoHighLevel MCP Server SOURCEbusybee3333/go-high-level-mcp-2026-complete
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/busybee3333-go-high-level-mcp-2026-complete/disconnect-integration.md

What disconnect_integration does on GoHighLevel MCP Server

AI agents use disconnect_integration to create or update resources in GoHighLevel MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GoHighLevel MCP Server environment.

Why disconnect_integration is rated Medium

Disconnecting an integration modifies the system state reversibly (the integration can be reconnected), making this a Write operation rather than Destructive. However, it carries medium severity because disconnecting integrations could disrupt dependent workflows, data synchronization, and automated messaging systems.

From the tool's definition Tool name 'disconnect_integration' and description 'Disconnect a third-party integration' indicate modification of system configuration by removing an active integration connection.

Questions about disconnect_integration

What does the disconnect_integration tool do? +

Disconnect a third-party integration. It is categorised as a Write tool in the GoHighLevel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on disconnect_integration? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for disconnect_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.

What risk level is disconnect_integration? +

disconnect_integration is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit disconnect_integration? +

Yes. Add a rate_limit block to the disconnect_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.

How do I block disconnect_integration completely? +

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

What MCP server provides disconnect_integration? +

disconnect_integration is provided by the GoHighLevel MCP Server MCP server (busybee3333/go-high-level-mcp-2026-complete). 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

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