create_custom_provider_config

Create new payment config for a location

SERVERGhl SOURCEghl-mcp-server

Medium RISK CLASS

Category Write

Parameters 33 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ghl/create-custom-provider-config.md

WHAT IT DOES

What create_custom_provider_config does on Ghl

AI agents use create_custom_provider_config to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.

Parameter	Type	Required	Description
`live`	object	Yes	Live payment configuration
`test`	object	Yes	Test payment configuration
`locationId`	string	Yes	Location ID

Parameters from the server's own tool schema.

RISK

Why create_custom_provider_config is rated Medium

This tool creates a new payment configuration, which is a reversible write operation. While it operates in a financial domain (payment config), it does not directly move money or commit financial obligations—it only sets up configuration. Classified as Write rather than Financial because the tool itself configures infrastructure rather than executing a transaction.

From the tool's definition Tool description states 'Create new payment config for a location' — this creates new configuration data. Related sibling tools include financial operations (add_outbound_call, add_contact_to_campaign) suggesting a financial/payments context.

Risk signalsHandles credentials or secrets (live.apiKey)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_custom_provider_config safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_custom_provider_config, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every create_custom_provider_config call is checked against it from then on.

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 Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does create_custom_provider_config accept? +

create_custom_provider_config accepts 3 parameters: live, test, locationId. Required: live, test, locationId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_custom_provider_config? +

Register the Ghl 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 Ghl. 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 Ghl MCP server (ghl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ghl, and thousands of servers like it.

This server

All 253 Ghl tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →