AI agents call get_transaction_from_pending 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 |
|---|---|---|---|
txId | string | Yes | The transaction ID (hash) to look up in the pending pool |
network | string | — | Network name. Defaults to mainnet. |
Parameters from the server's own tool schema.
This tool retrieves transaction details from the pending pool without modifying, executing, or deleting any data. It is a read-only query operation that poses minimal risk if misused by an AI agent, as it only exposes transaction information that would be visible on the blockchain anyway.
From the tool's definition Tool name contains 'get_transaction' and description states 'Get the details of a specific transaction from the pending pool by its transaction ID' - both indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get the details of a specific transaction from the pending pool by its transaction ID. It is categorised as a Read tool in the Tron MCP Server, which means it retrieves data without modifying state.
get_transaction_from_pending accepts 2 parameters: txId, network. Required: txId. 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_from_pending: 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_from_pending 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_from_pending 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_from_pending. 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_from_pending 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 →