create_custom_provider_config · GoHighLevel MCP Server MCP

WHAT IT DOES

What create_custom_provider_config does on GoHighLevel MCP Server

AI agents use create_custom_provider_config to commit financial operations through GoHighLevel MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.

WHY IT NEEDS A POLICY

Why create_custom_provider_config needs a policy

This tool creates payment configuration for a location, which directly involves financial infrastructure setup. Misconfiguration or misuse could redirect payments, alter payment processing behavior, or enable financial fraud. Financial category applies as it commits financial obligations and infrastructure.

From the tool's definition Create new payment config for a location

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_custom_provider_config Approval-gated

Any call to create_custom_provider_config is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_custom_provider_config": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GoHighLevel MCP Server, so you can run agents against it safely.

FAQ

Questions about create_custom_provider_config

What does the create_custom_provider_config tool do? +

Create new payment config for a location. It is categorised as a Financial tool in the GoHighLevel MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on create_custom_provider_config? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for create_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 GoHighLevel MCP Server. Nothing to install.

What risk level is create_custom_provider_config? +

create_custom_provider_config is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit create_custom_provider_config? +

Yes. Add a rate_limit block to the create_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.

How do I block create_custom_provider_config completely? +

Set action: deny in the PolicyLayer policy for create_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.

What MCP server provides create_custom_provider_config? +

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