Get a specific transaction by its ID
AI agents call get_transaction_by_id to retrieve information from GoHighLevel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves transaction data by ID without side effects. Although it accesses financial transaction records (which could be sensitive), the action itself is read-only retrieval. It does not move money, create financial obligations, modify records, or execute operations. The blast radius of misuse is limited to information disclosure rather than financial harm or irreversible changes.
From the tool's definition Tool name is 'get_transaction_by_id' and description states 'Get a specific transaction by its ID' - purely a retrieval operation with no modification, deletion, or financial movement involved.
Documented attack patterns abuse exactly the kind of access get_transaction_by_id gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GoHighLevel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_transaction_by_id:
{
"version": "1",
"default": "deny",
"tools": {
"get_transaction_by_id": {}
}
}get_transaction_by_id is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a specific transaction by its ID. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GoHighLevel MCP Server 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 GoHighLevel MCP Server. 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 GoHighLevel MCP Server MCP server (mastanley13/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 255 GoHighLevel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
255 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.