Create an unsigned TRX transfer transaction. The recipient account will be auto-activated if it does not exist. Returns an unsigned transaction object that must be signed before broadcasting.
AI agents use create_transaction 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 |
|---|---|---|---|
amount | integer | Yes | Transfer amount in SUN (1 TRX = 1,000,000 SUN) |
network | string | — | Network name. Defaults to mainnet. |
toAddress | string | Yes | Recipient address (Base58) |
ownerAddress | string | Yes | Sender address (Base58) |
Parameters from the server's own tool schema.
This tool creates a TRX transfer transaction, which is a financial operation. However, since it only creates an *unsigned* transaction object that still requires signing and broadcasting before any funds move, it does not by itself execute the financial transfer. The actual financial effect is deferred to the signing and broadcasting steps.
From the tool's definition Create an unsigned TRX transfer transaction. Returns an unsigned transaction object that must be signed before broadcasting.
Attacks that exploit this kind of access
Create an unsigned TRX transfer transaction. The recipient account will be auto-activated if it does not exist. Returns an unsigned transaction object that must be signed before broadcasting. 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_transaction accepts 4 parameters: amount, network, toAddress, ownerAddress. Required: amount, toAddress, ownerAddress. 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_transaction: 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_transaction 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_transaction 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_transaction. 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_transaction 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 →