Get your Merx account balance (TRX, USDT, locked). Requires MERX_API_KEY.
AI agents call get_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 retrieves financial information (account balance in TRX, USDT, and locked amounts) but does not modify, transfer, spend, or commit funds. It is purely informational. While the data retrieved is financially sensitive, the tool itself has no blast radius—misuse would expose information but not move money or create obligations. Severity is low because the tool only reads data.
From the tool's definition Tool description states 'Get your Merx account balance' — a retrieval operation with no side effects. The verb 'Get' and the readonly nature of querying account balance confirm this is a Read category tool.
Attacks that exploit this kind of access
Get your Merx account balance (TRX, USDT, locked). Requires MERX_API_KEY. 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_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_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_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_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_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 →