AI agents call get_burn_trx 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. |
Parameters from the server's own tool schema.
This tool performs a simple data retrieval operation querying aggregate statistics about burned TRX from historical transaction fees. It has no ability to modify state, execute code, delete data, or move funds. The query returns informational blockchain metrics only, making it a straightforward Read operation with minimal risk even if misused by an AI agent.
From the tool's definition Tool description explicitly states 'Query the total amount of TRX burned' - a read-only operation that retrieves historical blockchain data without side effects.
Attacks that exploit this kind of access
Query the total amount of TRX burned from on-chain transaction fees since No. 54 Committee Proposal took effect. It is categorised as a Read tool in the Tron MCP Server, which means it retrieves data without modifying state.
get_burn_trx accepts 1 parameter: network. 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_burn_trx: 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_burn_trx 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_burn_trx 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_burn_trx. 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_burn_trx 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 →