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 create or update resources in GoHighLevel MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GoHighLevel MCP Server environment.

WHY IT NEEDS A POLICY

Why create_custom_provider_config needs a policy

The tool creates (Write) a new payment configuration, which is reversible (can be deleted or modified). While payment-related, it configures infrastructure rather than moving money directly, so it does not meet the Financial category threshold. However, misconfigurations could expose payment credentials or redirect funds, making severity high.

From the tool's definition Tool name is 'create_custom_provider_config' and description states 'Create new payment config for a location' — this creates a new configuration object for payment processing.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_custom_provider_config Rate-limited

create_custom_provider_config stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_custom_provider_config": {
      "limits": [
        {
          "counter": "create_custom_provider_config_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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 Write tool in the GoHighLevel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

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 Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

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 (thinkbedo/gohighlevel_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.