AI agents call get_block_balance 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 |
|---|---|---|---|
hash | string | Yes | Block hash (64-char hex string) |
number | integer | Yes | Block height number |
network | string | — | Network name. Defaults to mainnet. |
Parameters from the server's own tool schema.
This tool retrieves historical blockchain data (balance change operations) for analytical or informational purposes. It has no capability to modify state, execute code, delete data, or move funds. The worst-case misuse would be information disclosure, which is low severity. The requirement for specific block identifiers limits its blast radius.
From the tool's definition Tool name 'get_block_balance' and description 'Get all balance change operations in a block' clearly indicate data retrieval with no side effects.
Attacks that exploit this kind of access
Get all balance change operations in a block. Requires block hash and block number. Note: requires the node to enable historical balance query. It is categorised as a Read tool in the Tron MCP Server, which means it retrieves data without modifying state.
get_block_balance accepts 3 parameters: hash, number, network. Required: hash, number. 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_balance: 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_balance 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_balance 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_balance. 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_balance 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 →