Delete an existing custom payment provider integration
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.
Deleting a payment provider integration is a destructive action that cannot be undone without reconfiguring the system. This impacts business operations, payment processing, and customer transactions. While not a direct financial transaction, destruction of payment infrastructure poses high risk if triggered by an AI agent without proper intent confirmation.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete an existing custom payment provider integration' — this irreversibly removes a configured payment system.
Attacks that exploit this kind of access
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.
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.
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 GoHighLevel MCP Server MCP server (mindflowedstudios/mindflowed_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →