AI agents call get_account 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 |
|---|---|---|---|
address | string | Yes | Account address (Base58 or Hex) |
network | string | — | Network name. Defaults to mainnet. |
Parameters from the server's own tool schema.
This tool retrieves account metadata and state information from the TRON blockchain. It performs a query operation with no side effects—it neither modifies state, executes transactions, deletes data, nor moves funds. The highest risk is information disclosure of publicly available blockchain data, which is minimal.
From the tool's definition Tool name 'get_account' and description 'Get full account information including balance, resources, permissions, frozen balance, and votes' indicate data retrieval with no modification or execution of transactions.
Attacks that exploit this kind of access
Get full account information including balance, resources, permissions, frozen balance, and votes. It is categorised as a Read tool in the Tron MCP Server, which means it retrieves data without modifying state.
get_account accepts 2 parameters: address, network. Required: address. 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_account: 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_account 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_account 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_account. 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_account 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 →