AI agents call get_block_by_limit_next 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 |
|---|---|---|---|
endNum | integer | Yes | End block height (exclusive) |
network | string | — | Network name. Defaults to mainnet. |
startNum | integer | Yes | Start block height (inclusive) |
Parameters from the server's own tool schema.
This tool queries blockchain data by retrieving blocks within a specified height range. It is a read-only operation with no side effects on the blockchain state. The retrieval of historical block data does not modify, execute, or destroy any resources, making it a straightforward Read operation with minimal security risk.
From the tool's definition Tool name contains 'get' and description states 'Retrieve a list of block objects' with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Retrieve a list of block objects within the specified block height range [startNum, endNum). It is categorised as a Read tool in the Tron MCP Server, which means it retrieves data without modifying state.
get_block_by_limit_next accepts 3 parameters: endNum, network, startNum. Required: endNum, startNum. 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_limit_next: 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_limit_next 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_limit_next 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_limit_next. 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_limit_next 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 →