This record as markdown: /tools/ghl/get-transaction-by-id.md
What get_transaction_by_id does on Ghl
AI agents call get_transaction_by_id 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) |
altType | string | Yes | Alt Type (type of identifier) |
locationId | string | — | Location ID (sub-account ID) |
transactionId | string | Yes | ID of the transaction to retrieve |
Parameters from the server's own tool schema.
Why get_transaction_by_id is rated Low
This is a straightforward data retrieval operation. It queries existing transaction records and returns information, with no ability to modify, delete, or execute actions. While transaction data may be sensitive, the read-only nature and narrow scope (retrieving a single transaction by ID) make this a low-severity Read operation.
From the tool's definition Tool name is 'get_transaction_by_id' and description states 'Get a specific transaction by its ID' - retrieves transaction data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_transaction_by_id 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 get_transaction_by_id, this is the rule to start with:
get_transaction_by_id 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 get_transaction_by_id call is checked against it from then on.
Questions about get_transaction_by_id
Get a specific transaction by its ID. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_transaction_by_id accepts 4 parameters: altId, altType, locationId, transactionId. Required: altId, altType, transactionId. 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 get_transaction_by_id: 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.
get_transaction_by_id 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 get_transaction_by_id 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 get_transaction_by_id. 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.
get_transaction_by_id 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