This record as markdown: /tools/ghl/create-order-fulfillment.md
What create_order_fulfillment does on Ghl
AI agents use create_order_fulfillment 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 |
|---|---|---|---|
altId | string | Yes | Location ID or Agency ID |
items | array | Yes | Items being fulfilled |
altType | string | Yes | Alt Type |
orderId | string | Yes | ID of the order to fulfill |
trackings | array | Yes | Fulfillment tracking information |
notifyCustomer | boolean | Yes | Whether to notify the customer |
Parameters from the server's own tool schema.
Why create_order_fulfillment is rated Medium
This tool creates/adds new data (a fulfillment record) but does not delete or execute arbitrary code. It is reversible (fulfillments can typically be modified or voided). The impact is limited to order management within the GoHighLevel system. Severity is medium because creating incorrect fulfillments could disrupt order processing and customer operations, but the effect is contained and potentially remediable.
From the tool's definition Tool name 'create_order_fulfillment' and description 'Create a fulfillment for an order' indicate creation of a new fulfillment record.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs create_order_fulfillment 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_order_fulfillment, this is the rule to start with:
create_order_fulfillment 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 create_order_fulfillment call is checked against it from then on.
Questions about create_order_fulfillment
Create a fulfillment for an order. 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.
create_order_fulfillment accepts 6 parameters: altId, items, altType, orderId, trackings, notifyCustomer. Required: altId, items, altType, orderId, trackings, notifyCustomer. 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_order_fulfillment: 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_order_fulfillment 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 create_order_fulfillment 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_order_fulfillment. 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_order_fulfillment 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