AI agents use generate_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.
Account generation creates new data artifacts (keys and addresses) that can be stored and used for subsequent blockchain operations. This is reversible in the sense that the generated account can be abandoned without using it, but the creation itself is a write operation that produces persistent state.
From the tool's definition Tool generates and returns a new TRON account with privateKey, publicKey, and address. This creates a new cryptographic keypair that constitutes a persistent digital asset.
Attacks that exploit this kind of access
Generate a new TRON account offline (keypair generation). Returns privateKey, publicKey, and address. No network interaction needed. 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.
Register the Tron MCP server in PolicyLayer and add a rule for generate_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.
generate_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 generate_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 generate_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.
generate_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 →