payments_create_integration

Create new integration

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Medium RISK CLASS

Category Write

Parameters 76 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/payments-create-integration.md

WHAT IT DOES

What payments_create_integration does on Ghl

AI agents use payments_create_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	The name of the custom provider
`imageUrl`	string	Yes	Public image url for logo of the payment gateway displayed on the payments integrations page.
`queryUrl`	string	Yes	The url used for querying payments related events. Ex. verify, refund, subscription etc.
`locationId`	string	—	Location id Defaults to GHL_LOCATION_ID when omitted.
`description`	string	Yes	Description of payment gateway. Shown on the payments integrations page as subtext
`paymentsUrl`	string	Yes	This url will be loaded in iFrame to start a payment session.
`supportsSubscriptionSchedule`	boolean	Yes	Whether the config supports subscription schedule or not. true represents config supports subscription schedule

Parameters from the server's own tool schema.

RISK

Why payments_create_integration is rated Medium

An AI agent can call payments_create_integration faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

payments_create_integration Rate-limited

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

FAQ

Questions about payments_create_integration

What does the payments_create_integration tool do? +

Create new 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 payments_create_integration accept? +

payments_create_integration accepts 7 parameters: name, imageUrl, queryUrl, locationId, description, paymentsUrl, supportsSubscriptionSchedule. Required: name, imageUrl, queryUrl, description, paymentsUrl, supportsSubscriptionSchedule. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on payments_create_integration? +

Register the Ghl MCP server in PolicyLayer and add a rule for payments_create_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 payments_create_integration? +

payments_create_integration is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit payments_create_integration? +

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

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

payments_create_integration is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). 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 569 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 →