This record as markdown: /tools/aiwerk-mcp-server-ghl/payments-create-coupon.md
What payments_create_coupon does on Ghl
AI agents use payments_create_coupon 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 |
|---|---|---|---|
code | string | Yes | Coupon Code |
name | string | Yes | Coupon Name |
altId | string | — | Location Id Defaults to GHL_LOCATION_ID when omitted. |
altType | string | — | Alt Type Defaults to GHL_LOCATION_ID when omitted. |
endDate | string | — | End date in YYYY-MM-DDTHH:mm:ssZ format |
startDate | string | Yes | Start date in YYYY-MM-DDTHH:mm:ssZ format |
productIds | array | — | Product Ids |
usageLimit | number | — | Max number of times coupon can be used |
discountType | string | Yes | Discount Type |
discountValue | number | Yes | Discount Value |
limitPerCustomer | boolean | — | Limits whether a coupon can be redeemed only once per customer. |
applyToFuturePayments | boolean | — | Is Coupon applicable on upcoming subscription transactions |
Parameters from the server's own tool schema.
Why payments_create_coupon is rated Medium
An AI agent can call payments_create_coupon 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.
Risk signalsAccepts freeform code/query input (code) · High parameter count (16 properties)
Attacks that exploit this kind of access
The rule that runs payments_create_coupon 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_coupon, this is the rule to start with:
payments_create_coupon 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every payments_create_coupon call is checked against it from then on.
Questions about payments_create_coupon
Create Coupon. 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.
payments_create_coupon accepts 12 parameters: code, name, altId, altType, endDate, startDate, productIds, usageLimit, discountType, discountValue, limitPerCustomer, applyToFuturePayments. Required: code, name, startDate, discountType, discountValue. 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 payments_create_coupon: 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.
payments_create_coupon is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the payments_create_coupon 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 payments_create_coupon. 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.
payments_create_coupon 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.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue