This record as markdown: /tools/ghl/update-coupon.md
What update_coupon does on Ghl
AI agents use update_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 |
|---|---|---|---|
id | string | Yes | Coupon ID |
code | string | Yes | Coupon code |
name | string | Yes | Coupon name |
altId | string | Yes | Location ID |
altType | string | Yes | Alt Type |
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 that the coupon applies to |
usageLimit | number | — | Maximum number of times coupon can be used |
discountType | string | Yes | Type of discount |
discountValue | number | Yes | Discount value |
limitPerCustomer | boolean | — | Whether to limit coupon to once per customer |
Parameters from the server's own tool schema.
Why update_coupon is rated Medium
This tool creates or modifies data (a coupon record) in a reversible way. It is not a Read operation (no retrieval only), not Destructive (the coupon is not deleted, only updated), not Execute (no arbitrary code execution), and not Financial (no money movement, though coupons have business value).
From the tool's definition Tool name is 'update_coupon' and description states 'Update an existing coupon', which modifies existing data in a reversible manner without deleting or destroying it.
Risk signalsAccepts freeform code/query input (code) · High parameter count (17 properties)
Attacks that exploit this kind of access
The rule that runs update_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 update_coupon, this is the rule to start with:
update_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 update_coupon call is checked against it from then on.
Questions about update_coupon
Update an existing 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.
update_coupon accepts 12 parameters: id, code, name, altId, altType, endDate, startDate, productIds, usageLimit, discountType, discountValue, limitPerCustomer. Required: id, code, name, altId, altType, 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 update_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.
update_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 update_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 update_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.
update_coupon 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.
This server
Across the catalogue