AI agents call get_block_by_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 performs a straightforward data retrieval operation on immutable blockchain records. It queries and returns existing block information (header and transactions) by height parameter, with no capability to modify state, execute code, or trigger side effects. The read-only nature and lack of side effects place it squarely in the Read category with low severity.
From the tool's definition Tool name 'get_block_by_num' and description 'Query block by block height. Returns block header and transaction list.' indicate a read-only operation that retrieves blockchain data without modification or execution.
Attacks that exploit this kind of access
Query block by block height. Returns block header and transaction list. It is categorised as a Read tool in the Tron MCP Server, which means it retrieves data without modifying state.
get_block_by_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_block_by_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_block_by_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_block_by_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_block_by_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_block_by_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 →