delete_custom_provider_integration

Delete an existing custom payment provider integration

SERVERGoHighLevel MCP Server SOURCEhridayshah7/gohighlevel-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hridayshah7-gohighlevel-mcp/delete-custom-provider-integration.md

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 is rated Critical

The tool irreversibly deletes payment provider integration configuration, which cannot be undone. This is a destructive action that removes business-critical payment processing setup. While not directly moving money (Financial), it could disrupt financial operations if misconfigured by an agent. Destructive is the primary category due to the permanent deletion of configuration.

From the tool's definition Tool name contains 'delete' and description states 'Delete an existing custom payment provider integration' - both indicate irreversible removal of configuration data.

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

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