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 retrieves transaction information by ID without creating, modifying, deleting, or executing any operations. While transactions are financial in nature, the tool itself only reads data—it does not move money, commit financial obligations, or execute financial transactions. The Read category applies to all data retrieval operations regardless of the data type's sensitivity.
From the tool's definition Tool name 'get_transaction_by_id' and description 'Get a specific transaction by its ID' indicate a read-only retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
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 (tailormadeweddings/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →