payments_list_transactions

List Transactions

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Low RISK CLASS

Category Read

Parameters 122 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/payments-list-transactions.md

WHAT IT DOES

What payments_list_transactions does on Ghl

AI agents call payments_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	AltId is the unique identifier e.g: location id.
`endAt`	string	—	Closing interval of transactions.
`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 transaction for searching.
`altType`	string	Yes	AltType is the type of identifier.
`startAt`	string	—	Starting interval of transactions.
`entityId`	string	—	Entity id for filtering of transactions.
`contactId`	string	—	Contact id for filtering of transactions.
`locationId`	string	—	LocationId is the id of the sub-account. Defaults to GHL_LOCATION_ID when omitted.
`paymentMode`	string	—	Mode of payment.
`subscriptionId`	string	—	Subscription id for filtering of transactions.

Parameters from the server's own tool schema.

RISK

Why payments_list_transactions is rated Low

Even though payments_list_transactions 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 (14 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs payments_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 payments_list_transactions, this is the rule to start with:

payments_list_transactions Allowed

payments_list_transactions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "payments_list_transactions": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every payments_list_transactions call is checked against it from then on.

FAQ

Questions about payments_list_transactions

What does the payments_list_transactions tool do? +

List Transactions. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.

What parameters does payments_list_transactions accept? +

payments_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.

How do I enforce a policy on payments_list_transactions? +

Register the Ghl MCP server in PolicyLayer and add a rule for payments_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.

What risk level is payments_list_transactions? +

payments_list_transactions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit payments_list_transactions? +

Yes. Add a rate_limit block to the payments_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.

How do I block payments_list_transactions completely? +

Set action: deny in the PolicyLayer policy for payments_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.

What MCP server provides payments_list_transactions? +

payments_list_transactions 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.

KEEP EXPLORING

More on Ghl, and thousands of servers like it.

This server

All 569 Ghl tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →