AI agents use update_account to create or update resources in Tron — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tron environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
network | string | — | Network name. Defaults to mainnet. |
accountName | string | Yes | New account name |
Parameters from the server's own tool schema.
This tool modifies account metadata (the account name) on the TRON blockchain. It is a Write operation because it creates or modifies data reversibly within the constraints of the blockchain protocol. Severity is medium because changing an account name could impact account identification and user experience, but does not involve financial transactions, data deletion, or code execution.
From the tool's definition Tool description states 'Update the name of the configured wallet's account', which is a modification operation. The constraint 'Can only be set once' indicates this is a reversible write operation (cannot be undone after first use, but does not destroy data).
Attacks that exploit this kind of access
Update the name of the configured wallet's account. Can only be set once. It is categorised as a Write tool in the Tron MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_account accepts 2 parameters: network, accountName. Required: accountName. 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 update_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.
update_account is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_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 →