AI agents call get_transaction_info_by_block_num 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 |
|---|---|---|---|
num | integer | Yes | Block height number |
network | string | — | Network name. Defaults to mainnet. |
Parameters from the server's own tool schema.
This tool retrieves transaction receipts and information from a specified block. It is a read-only query operation with no side effects, no state changes, and no ability to transfer funds or execute code. The only input is a block number, which is a safe parameter. Misuse by an AI agent would be limited to information disclosure or DoS via excessive requests, both low-severity risks.
From the tool's definition Tool name contains 'get' and description states 'Get TransactionInfo (receipts) for all transactions in a specific block height' — a pure query operation that retrieves historical blockchain data without modification.
Attacks that exploit this kind of access
Get TransactionInfo (receipts) for all transactions in a specific block height. It is categorised as a Read tool in the Tron MCP Server, which means it retrieves data without modifying state.
get_transaction_info_by_block_num accepts 2 parameters: num, network. Required: num. 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_info_by_block_num: 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_info_by_block_num 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_info_by_block_num 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_info_by_block_num. 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_info_by_block_num 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 →