get_account_info

Inspect any TRON address. Aliases: check_address, get_address_info, get_wallet_info, address_info, account_status. Read the full on-chain state of ANY TRON address (does not have to be your own): TRX balance, free + delegated energy, free + delegated bandwidth, frozen TRX, account creation timest...

Server MERX - TRON Resource Exchange Hovsteder/merx-mcp
Category Read
Risk class Low
Parameters 00 required

What get_account_info does on MERX - TRON Resource Exchange

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

Why get_account_info needs a policy

This is a pure read operation that queries public blockchain data without any modification, creation, deletion, or execution of code. The tool requires no authentication and performs only information retrieval. While it can inspect any address (not just the caller's own), this remains a read-only query with no blast radius beyond information disclosure of public blockchain data.

From the tool's definition Tool description explicitly states it 'Inspect[s] any TRON address' and 'Read the full on-chain state', retrieving TRX balance, energy, bandwidth, frozen TRX, and account creation timestamp. No side effects: 'does not modify data'.

Questions about get_account_info

What does the get_account_info tool do? +

Inspect any TRON address. Aliases: check_address, get_address_info, get_wallet_info, address_info, account_status. Read the full on-chain state of ANY TRON address (does not have to be your own): TRX balance, free + delegated energy, free + delegated bandwidth, frozen TRX, account creation timestamp. Use this to check if an address has enough resources before sending a transaction, or to inspect any TRON wallet. No auth required, no API key needed. It is categorised as a Read tool in the MERX - TRON Resource Exchange MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_account_info? +

Register the MERX - TRON Resource Exchange MCP server in PolicyLayer and add a rule for get_account_info: 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.

What risk level is get_account_info? +

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

Can I rate-limit get_account_info? +

Yes. Add a rate_limit block to the get_account_info 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_account_info completely? +

Set action: deny in the PolicyLayer policy for get_account_info. 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_account_info? +

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

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