disconnect_custom_provider_config
Disconnect existing payment config for a location
This record as markdown: /tools/ghl/disconnect-custom-provider-config.md
What disconnect_custom_provider_config does on Ghl
AI agents use disconnect_custom_provider_config to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
liveMode | boolean | Yes | Whether to disconnect live or test mode config |
locationId | string | Yes | Location ID |
Parameters from the server's own tool schema.
Why disconnect_custom_provider_config is rated Medium
This tool removes or disables an existing payment configuration, which is a reversible write operation (the config can be reconfigured later). It does not permanently delete the underlying account data, but it does alter a critical system setting.
From the tool's definition Disconnect existing payment config for a location — explicitly modifies/removes payment configuration data.
Attacks that exploit this kind of access
The rule that runs disconnect_custom_provider_config 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 disconnect_custom_provider_config, this is the rule to start with:
disconnect_custom_provider_config stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every disconnect_custom_provider_config call is checked against it from then on.
Questions about disconnect_custom_provider_config
Disconnect existing payment config for a location. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
disconnect_custom_provider_config accepts 2 parameters: liveMode, locationId. Required: liveMode, locationId. 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 disconnect_custom_provider_config: 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.
disconnect_custom_provider_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the disconnect_custom_provider_config 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 disconnect_custom_provider_config. 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.
disconnect_custom_provider_config 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.
This server
Across the catalogue