create_custom_provider_integration

Create a new custom payment provider integration

SERVERGhl SOURCEghl-mcp-server

Medium RISK CLASS

Category Write

Parameters 66 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-integration.md

WHAT IT DOES

What create_custom_provider_integration does on Ghl

AI agents use create_custom_provider_integration 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
`name`	string	Yes	Name of the custom provider
`imageUrl`	string	Yes	Public image URL for the payment gateway logo
`queryUrl`	string	Yes	URL for querying payment events
`locationId`	string	Yes	Location ID
`description`	string	Yes	Description of the payment gateway
`paymentsUrl`	string	Yes	URL to load in iframe for payment session

Parameters from the server's own tool schema.

RISK

Why create_custom_provider_integration is rated Medium

The tool creates a new integration, which is a reversible write operation that modifies system state. While it involves payment providers (suggesting financial domain), the action itself is configuration/setup rather than moving money.

From the tool's definition Tool name specifies "create" and description states "Create a new custom payment provider integration" - this is a creation operation that modifies system configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_custom_provider_integration 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_integration, this is the rule to start with:

create_custom_provider_integration Rate-limited

create_custom_provider_integration 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_integration": {
      "limits": [
        {
          "counter": "create_custom_provider_integration_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_integration call is checked against it from then on.

FAQ

Questions about create_custom_provider_integration

What does the create_custom_provider_integration tool do? +

Create a new custom payment provider integration. 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_integration accept? +

create_custom_provider_integration accepts 6 parameters: name, imageUrl, queryUrl, locationId, description, paymentsUrl. Required: name, imageUrl, queryUrl, locationId, description, paymentsUrl. 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_integration? +

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

What risk level is create_custom_provider_integration? +

create_custom_provider_integration 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_integration? +

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

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

create_custom_provider_integration 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 →