This record as markdown: /tools/ghl/create-whitelabel-integration-provider.md
What create_whitelabel_integration_provider does on Ghl
AI agents use create_whitelabel_integration_provider to commit financial operations through Ghl, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
altId | string | Yes | Location ID or company ID based on altType |
title | string | Yes | The title or name of the integration provider |
altType | string | Yes | Alt Type |
imageUrl | string | Yes | The URL to an image representing the integration provider |
provider | string | Yes | The type of payment provider |
uniqueName | string | Yes | A unique name for the integration provider (lowercase, hyphens only) |
description | string | Yes | A brief description of the integration provider |
Parameters from the server's own tool schema.
Why create_whitelabel_integration_provider is rated Critical
This tool creates payment integration infrastructure, directly relating to financial systems and payment processing. Setting up payment providers can commit financial obligations, enable money movement, and establish billing relationships, making this a Financial category tool with high severity due to the potential blast radius of misconfigured payment providers.
From the tool's definition Create a white-label integration provider for payments
Attacks that exploit this kind of access
The rule that runs create_whitelabel_integration_provider 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_whitelabel_integration_provider, this is the rule to start with:
Any call to create_whitelabel_integration_provider is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every create_whitelabel_integration_provider call is checked against it from then on.
Questions about create_whitelabel_integration_provider
Create a white-label integration provider for payments. It is categorised as a Financial tool in the Ghl MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
create_whitelabel_integration_provider accepts 7 parameters: altId, title, altType, imageUrl, provider, uniqueName, description. Required: altId, title, altType, imageUrl, provider, uniqueName, description. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for create_whitelabel_integration_provider: 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.
create_whitelabel_integration_provider is a Financial 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 create_whitelabel_integration_provider 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 create_whitelabel_integration_provider. 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.
create_whitelabel_integration_provider 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.
More on Ghl, and thousands of servers like it.
Across the catalogue