AI agents use send_trx to commit financial operations through Tron — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves real cryptocurrency (TRX) on the TRON blockchain, constituting a financial transaction that is irreversible once confirmed. Misuse by an AI agent could result in loss of funds with no ability to recover them, making this critical severity.
From the tool's definition 'Send TRX to an address' — directly transfers TRX cryptocurrency to a specified address
Attacks that exploit this kind of access
Send TRX 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.
Register the Tron MCP server in PolicyLayer and add a rule for send_trx: 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.
send_trx 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 send_trx 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 send_trx. 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.
send_trx is provided by the Tron MCP server (netts-official/tron_mcp_server). 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 →