Get events from the most recent block that contains events (skips empty blocks). Results may be limited by the API default page size and subject to event indexing lag. For precise control, use get_events_by_block_number with a specific block number and limit/fingerprint pagination.
AI agents call get_events_of_latest_block 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 |
|---|---|---|---|
network | string | — | Network name. Defaults to mainnet. |
onlyConfirmed | boolean | — | Only return confirmed events |
Parameters from the server's own tool schema.
This tool only performs data retrieval from the blockchain ledger—it queries and returns event logs from blocks. There is no creation, modification, deletion, code execution, or financial transaction involved. It is a simple read operation that does not alter blockchain state or trigger any external actions. The mention of 'pagination' and 'API default page size' further confirms this is a bounded query operation.
From the tool's definition Tool description states it retrieves/queries events from the latest block with events. Key verbs are 'get' and 'results may be limited', indicating read-only data retrieval with no modification or execution. Returns event data without side effects.
Attacks that exploit this kind of access
Get events from the most recent block that contains events (skips empty blocks). Results may be limited by the API default page size and subject to event indexing lag. For precise control, use get_events_by_block_number with a specific block number and limit/fingerprint pagination. It is categorised as a Read tool in the Tron MCP Server, which means it retrieves data without modifying state.
get_events_of_latest_block accepts 2 parameters: network, onlyConfirmed. 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_of_latest_block: 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_of_latest_block 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_of_latest_block 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_of_latest_block. 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_of_latest_block 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 →