AI agents call list_wallets 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 and displays wallet information without any side effects. It is informational only and does not create, modify, delete, or execute any blockchain operations. The severity is low because wallet listing is non-sensitive data retrieval that does not enable financial transactions or destructive operations on its own.
From the tool's definition Tool description explicitly states it 'List all available wallets' and 'Returns wallet IDs, types, and addresses' — purely a query operation with no modification, deletion, or execution of transactions.
Attacks that exploit this kind of access
List all available wallets. Returns wallet IDs, types, and addresses. Use select_wallet to switch between them. 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 list_wallets: 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.
list_wallets 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 list_wallets 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 list_wallets. 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.
list_wallets 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 →