Get events emitted in a specific block. Supports pagination via limit and fingerprint. Preferred over get_events_of_latest_block when you need precise block targeting or full event retrieval.
AI agents call get_events_by_block_number 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 |
|---|---|---|---|
limit | number | — | Max events per page (default 20, max 200) |
network | string | — | Network name. Defaults to mainnet. |
blockNumber | number | Yes | The block number to query events for |
fingerprint | string | — | Pagination token from previous response |
onlyConfirmed | boolean | — | Only return confirmed events |
Parameters from the server's own tool schema.
This tool queries and retrieves historical event data from the TRON blockchain by block number. It is a read-only operation with no side effects—it does not create transactions, transfer funds, modify state, or execute code. The mention of pagination parameters (limit, fingerprint) further confirms this is a data retrieval utility.
From the tool's definition Tool name and description indicate retrieval operation: 'Get events emitted in a specific block' with 'pagination via limit and fingerprint' for querying blockchain data. No modification, deletion, or execution capabilities mentioned.
Attacks that exploit this kind of access
Get events emitted in a specific block. Supports pagination via limit and fingerprint. Preferred over get_events_of_latest_block when you need precise block targeting or full event retrieval. It is categorised as a Read tool in the Tron MCP Server, which means it retrieves data without modifying state.
get_events_by_block_number accepts 5 parameters: limit, network, blockNumber, fingerprint, onlyConfirmed. Required: blockNumber. 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_events_by_block_number: 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_events_by_block_number 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_events_by_block_number 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_events_by_block_number. 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_events_by_block_number 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 →