This record as markdown: /tools/ghl/list-orders.md
What list_orders does on Ghl
AI agents call 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 | Alt ID (unique identifier like location ID) |
endAt | string | — | Ending date interval for orders (YYYY-MM-DD) |
limit | number | — | Maximum number of items per page |
offset | number | — | Starting index for pagination |
search | string | — | Search term for order name |
status | string | — | Order status filter |
altType | string | Yes | Alt Type (type of identifier) |
startAt | string | — | Starting date interval for orders (YYYY-MM-DD) |
contactId | string | — | Contact ID for filtering orders |
locationId | string | — | Location ID (sub-account ID) |
paymentMode | string | — | Mode of payment (live/test) |
funnelProductIds | string | — | Comma-separated funnel product IDs |
Parameters from the server's own tool schema.
Why list_orders is rated Low
This tool retrieves order data with filtering and pagination capabilities. It has no side effects, does not create, modify, delete, or execute operations. It falls squarely into the Read category with low severity because misuse would only expose data visibility, not cause irreversible changes or financial transactions.
From the tool's definition Tool name 'list_orders' and description 'List orders with optional filtering and pagination' indicate a retrieval operation. The verb 'list' explicitly denotes querying/fetching data without modification.
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs 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 list_orders, this is the rule to start with:
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 list_orders call is checked against it from then on.
Questions about list_orders
List orders with optional filtering and pagination. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
list_orders accepts 12 parameters: altId, endAt, limit, offset, search, status, altType, startAt, contactId, locationId, paymentMode, funnelProductIds. Required: altId, altType. 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 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.
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 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 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.
list_orders 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