AI agents use create_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 |
|---|---|---|---|
address | string | Yes | Address to activate (Base58 or Hex) |
network | string | — | Network name. Defaults to mainnet. |
Parameters from the server's own tool schema.
Creating a new account on a blockchain is a write operation that irreversibly commits resources (bandwidth costs from the wallet) and establishes a new on-chain entity. While it consumes wallet resources, it is not itself a financial transfer (no money moved to another party), so it does not qualify as 'Financial'. It is not destructive because account creation is a normal, reversible blockchain operation.
From the tool's definition The tool 'create_account' activates a new account on the TRON network and explicitly costs bandwidth from the configured wallet, demonstrating it creates a new persistent resource on the blockchain.
Attacks that exploit this kind of access
Activate a new account on the TRON network. Costs bandwidth from the configured wallet. The target address must be generated beforehand. 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.
create_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 create_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.
create_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 create_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 create_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.
create_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 →