delete_custom_provider_integration

Delete an existing custom payment provider integration

Server GoHighLevel MCP Server tailormadeweddings/gohighlevel-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_custom_provider_integration does on GoHighLevel MCP Server

AI agents call delete_custom_provider_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_custom_provider_integration needs a policy

This tool irreversibly deletes a custom payment provider integration. Deletion cannot be undone and affects financial operations by removing a payment processing setup. While not moving money directly (Financial category), the destruction of a payment provider integration is a critical infrastructure change that could disrupt financial transactions.

From the tool's definition Tool name 'delete_custom_provider_integration' combined with description 'Delete an existing custom payment provider integration' explicitly performs a DELETE operation on a payment provider configuration.

Questions about delete_custom_provider_integration

What does the delete_custom_provider_integration tool do? +

Delete an existing custom payment provider integration. 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 delete_custom_provider_integration? +

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

What risk level is delete_custom_provider_integration? +

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.

Can I rate-limit delete_custom_provider_integration? +

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.

How do I block delete_custom_provider_integration completely? +

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.

What MCP server provides delete_custom_provider_integration? +

delete_custom_provider_integration is provided by the GoHighLevel MCP Server MCP server (tailormadeweddings/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.