AI agents call get_block_by_latest_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 | Number of latest blocks to retrieve (1-100) |
network | string | — | Network name. Defaults to mainnet. |
Parameters from the server's own tool schema.
This tool queries historical blockchain data without side effects. It retrieves already-finalized blocks ('latest solidified block') and returns them in a specified order. No state changes, contract execution, or financial transactions occur. This is a straightforward read-only query operation with minimal misuse risk—an agent cannot cause damage by retrieving block data.
From the tool's definition Tool performs 'Retrieve' operation on blockchain blocks with no modification capability. Description explicitly states retrieval of 'most recent N blocks' in 'descending order of height' with no write, deletion, or execution parameters.
Attacks that exploit this kind of access
Retrieve the most recent N blocks, starting from the latest solidified block in descending order of height. It is categorised as a Read tool in the Tron MCP Server, which means it retrieves data without modifying state.
get_block_by_latest_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_latest_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_latest_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_latest_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_latest_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_latest_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 →