select_wallet · Tron MCP: Risk & Policy

WHAT IT DOES

What select_wallet does on Tron

AI agents invoke select_wallet to trigger actions in Tron. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

PARAMETERS

Parameter	Type	Required	Description
`walletId`	string	Yes	The wallet ID to switch to

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why select_wallet needs a policy

Switching the active wallet changes which private key/account is used for all subsequent blockchain operations (transfers, contract calls, etc.). This is an Execute-level action because it triggers a runtime state change that determines the blast radius of any financial or destructive operations that follow. Misuse could redirect funds or sign transactions with an unintended wallet, making it high severity.

From the tool's definition Switch the active wallet at runtime

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

select_wallet Rate-limited

select_wallet stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "select_wallet": {
      "limits": [
        {
          "counter": "select_wallet_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Tron, so you can run agents against it safely.

FAQ

Questions about select_wallet

What does the select_wallet tool do? +

Switch the active wallet at runtime. Use list_wallets to see available wallet IDs. Only available in Encrypted Storage mode. It is categorised as a Execute tool in the Tron MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does select_wallet accept? +

select_wallet accepts 1 parameter: walletId. Required: walletId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on select_wallet? +

Register the Tron MCP server in PolicyLayer and add a rule for select_wallet: 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.

What risk level is select_wallet? +

select_wallet is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit select_wallet? +

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

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

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