AI agents call get_wallet_address 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.
This tool retrieves configuration data (the active wallet address) without modifying, executing, or affecting any blockchain state or financial transactions. It is purely informational. Even in the context of a blockchain server with financial capabilities, this specific tool only queries and returns existing data.
From the tool's definition Tool name is 'get_wallet_address' and description states 'Get the address of the configured wallet. Use this to verify which wallet is active.' The verb 'get' and the stated purpose of verification indicate a read-only query operation with no side effects.
Attacks that exploit this kind of access
Get the address of the configured wallet. Use this to verify which wallet is active. It is categorised as a Read tool in the Tron MCP Server, which means it retrieves data without modifying state.
Register the Tron MCP server in PolicyLayer and add a rule for get_wallet_address: 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_wallet_address 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_wallet_address 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_wallet_address. 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_wallet_address 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 →