This record as markdown: /tools/ghl/delete-custom-provider-integration.md
What delete_custom_provider_integration does on Ghl
AI agents call delete_custom_provider_integration to permanently remove resources in Ghl, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
locationId | string | Yes | Location ID |
Parameters from the server's own tool schema.
Why delete_custom_provider_integration is rated Critical
This tool irreversibly removes a custom payment provider integration. Deleting provider integrations cannot be undone without manual restoration and disrupts payment processing workflows. While not a direct financial transaction, it removes critical infrastructure for financial operations, making it Destructive rather than Financial. The high severity reflects the operational impact on payment systems.
From the tool's definition delete_custom_provider_integration — 'Delete an existing custom payment provider integration'
Attacks that exploit this kind of access
The rule that runs delete_custom_provider_integration 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 delete_custom_provider_integration, this is the rule to start with:
delete_custom_provider_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 Ghl, apply this rule, and every delete_custom_provider_integration call is checked against it from then on.
Questions about delete_custom_provider_integration
Delete an existing custom payment provider integration. It is categorised as a Destructive tool in the Ghl MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_custom_provider_integration accepts 1 parameter: locationId. Required: 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 delete_custom_provider_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 Ghl. Nothing to install.
delete_custom_provider_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_custom_provider_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_custom_provider_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_custom_provider_integration 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.
Across the catalogue