AI agents call get_transaction to retrieve information from Tron without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
txHash | string | Yes | Transaction hash |
network | string | — | Network name. Defaults to mainnet. |
Parameters from the server's own tool schema.
This tool only retrieves and returns transaction details based on a provided hash. It has no side effects, does not modify blockchain state, does not execute code or contracts, and does not move funds. It is a straightforward read-only query operation against the TRON blockchain.
From the tool's definition Tool name 'get_transaction' and description 'Get transaction details by transaction hash' indicate a query operation that retrieves existing transaction data without modifying or executing anything.
Attacks that exploit this kind of access
Get transaction details by transaction hash. It is categorised as a Read tool in the Tron MCP Server, which means it retrieves data without modifying state.
get_transaction accepts 2 parameters: txHash, network. Required: txHash. The full parameter table on this page comes from the server's own tool schema.
Register the Tron MCP server in PolicyLayer and add a rule for get_transaction: 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 Tron. Nothing to install.
get_transaction 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 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. 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 is provided by the Tron MCP server (@bankofai/mcp-server-tron). 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 →