list_transactions
List transactions with optional filtering and pagination
This record as markdown: /tools/ghl/list-transactions.md
What list_transactions does on Ghl
AI agents call list_transactions 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 transactions (YYYY-MM-DD) |
limit | number | — | Maximum number of items per page |
offset | number | — | Starting index for pagination |
search | string | — | Search term for transaction name |
altType | string | Yes | Alt Type (type of identifier) |
startAt | string | — | Starting date interval for transactions (YYYY-MM-DD) |
entityId | string | — | Entity ID for filtering transactions |
contactId | string | — | Contact ID for filtering transactions |
locationId | string | — | Location ID (sub-account ID) |
paymentMode | string | — | Mode of payment (live/test) |
subscriptionId | string | — | Subscription ID for filtering transactions |
Parameters from the server's own tool schema.
Why list_transactions is rated Low
This tool retrieves transaction data with filtering and pagination options. It performs no side effects, does not modify data, and does not execute operations. While transactions may be financial in nature, the tool itself only reads/lists existing transactions and poses no financial risk as it cannot move money or create obligations.
From the tool's definition Tool name is 'list_transactions' and description states 'List transactions with optional filtering and pagination', which are read-only operations that retrieve data without modifying or deleting it.
Risk signalsHigh parameter count (14 properties)
Attacks that exploit this kind of access
The rule that runs list_transactions 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_transactions, this is the rule to start with:
list_transactions 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_transactions call is checked against it from then on.
Questions about list_transactions
List transactions 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_transactions accepts 12 parameters: altId, endAt, limit, offset, search, altType, startAt, entityId, contactId, locationId, paymentMode, subscriptionId. 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_transactions: 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_transactions 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_transactions 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_transactions. 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_transactions 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