Quick TRX balance for a TRON address. No auth required.
AI agents call get_trx_balance to retrieve information from MERX - TRON Resource Exchange without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns balance data for a TRON address with no side effects. It is a read-only operation that retrieves information without modifying any state. The lack of authentication requirement and the passive nature of balance inquiry confirm it poses minimal risk as a Read category tool with low severity.
From the tool's definition Tool name 'get_trx_balance' and description 'Quick TRX balance for a TRON address' indicate retrieval of balance information. Description explicitly states 'No auth required' and contains no language suggesting modification, deletion, or financial movement.
Attacks that exploit this kind of access
Quick TRX balance for a TRON address. No auth required. It is categorised as a Read tool in the MERX - TRON Resource Exchange MCP Server, which means it retrieves data without modifying state.
Register the MERX - TRON Resource Exchange MCP server in PolicyLayer and add a rule for get_trx_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 MERX - TRON Resource Exchange. Nothing to install.
get_trx_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_trx_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_trx_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_trx_balance is provided by the MERX - TRON Resource Exchange MCP server (Hovsteder/merx-mcp). 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 →