get_block_by_id

Query block by block ID (hash). Returns block header and transaction list.

Server Tron @bankofai/mcp-server-tron
Category Read
Risk class Low
Parameters 21 required

What get_block_by_id does on Tron

AI agents call get_block_by_id 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.

ParameterTypeRequiredDescription
value string Yes Block hash / ID (64-char hex string)
network string Network name. Defaults to mainnet.

Parameters from the server's own tool schema.

Why get_block_by_id needs a policy

This tool retrieves blockchain data without side effects. It queries existing block information by ID and returns the block header and transaction list. No data is created, modified, deleted, or financial transactions are triggered. This is a straightforward read operation with minimal risk, appropriate for blockchain exploration and analysis.

From the tool's definition Tool name and description indicate a query operation: 'Query block by block ID' and 'Returns block header and transaction list.' These are read-only retrieval operations with no state modification.

Questions about get_block_by_id

What does the get_block_by_id tool do? +

Query block by block ID (hash). Returns block header and transaction list. It is categorised as a Read tool in the Tron MCP Server, which means it retrieves data without modifying state.

What parameters does get_block_by_id accept? +

get_block_by_id accepts 2 parameters: value, network. Required: value. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_block_by_id? +

Register the Tron MCP server in PolicyLayer and add a rule for get_block_by_id: 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.

What risk level is get_block_by_id? +

get_block_by_id is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_block_by_id? +

Yes. Add a rate_limit block to the get_block_by_id 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.

How do I block get_block_by_id completely? +

Set action: deny in the PolicyLayer policy for get_block_by_id. 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.

What MCP server provides get_block_by_id? +

get_block_by_id 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.