This record as markdown: /tools/aiwerk-mcp-server-ghl/payments-list-orders.md
What payments_list_orders does on Ghl
AI agents call payments_list_orders to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
altId | string | Yes | AltId is the unique identifier e.g: location id. |
endAt | string | — | Closing interval of orders. |
limit | number | — | The maximum number of items to be included in a single page of results |
offset | number | — | The starting index of the page, indicating the position from which the results should be retrieved. |
search | string | — | The name of the order for searching. |
status | string | — | Order status. |
startAt | string | — | Starting interval of orders. |
sourceId | string | — | Source id |
contactId | string | — | Contact id for filtering of orders. |
locationId | string | — | LocationId is the id of the sub-account. Defaults to GHL_LOCATION_ID when omitted. |
paymentMode | string | — | Mode of payment. |
paymentStatus | string | — | Payment Status of the Order |
Parameters from the server's own tool schema.
Why payments_list_orders is rated Low
Even though payments_list_orders only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
The rule that runs payments_list_orders 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_list_orders, this is the rule to start with:
payments_list_orders is read-only, so it stays allowed. 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_list_orders call is checked against it from then on.
Questions about payments_list_orders
List Orders. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
payments_list_orders accepts 12 parameters: altId, endAt, limit, offset, search, status, startAt, sourceId, contactId, locationId, paymentMode, paymentStatus. Required: altId. 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_list_orders: 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_list_orders is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the payments_list_orders 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_list_orders. 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_list_orders 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