AI agents use transfer_trc20 to commit financial operations through Tron — usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | Yes | Recipient address |
amount | string | — | Amount to send (raw amount with decimals) |
network | string | — | Network name. Defaults to mainnet. |
tokenAddress | string | Yes | The TRC20 token contract address |
Parameters from the server's own tool schema.
This tool directly moves cryptocurrency tokens (TRC20) between addresses, which constitutes a financial transaction. Even though the actual execution depends on being packaged into a transaction via sibling tools like 'broadcast_transaction', the transfer_trc20 function itself represents a financial commitment. Financial category supersedes all others per the severity hierarchy.
From the tool's definition Tool enables 'Transfer TRC20 tokens to an address' on a TRON blockchain MCP server. TRC20 is the TRON token standard analogous to ERC20. Transferring tokens represents movement of financial value and commits financial obligations.
Attacks that exploit this kind of access
Transfer TRC20 tokens to an address. It is categorised as a Financial tool in the Tron MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
transfer_trc20 accepts 4 parameters: to, amount, network, tokenAddress. Required: to, tokenAddress. 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 transfer_trc20: 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.
transfer_trc20 is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the transfer_trc20 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 transfer_trc20. 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.
transfer_trc20 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 →