Critical Risk →

transfer_trx

Send TRX to an address. Checks bandwidth, buys via Merx if needed. Signs and broadcasts on-chain. Requires TRON_PRIVATE_KEY.

Part of the MERX - TRON Resource Exchange MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

merx-mcp Financial

AI agents use transfer_trx to initiate financial transactions through MERX - TRON Resource Exchange. Financial operations involve real money and are irreversible once processed. Intercept blocks financial tools by default, requiring explicit human approval with transaction-level limits to prevent unauthorised spending.

transfer_trx moves real money. Without a policy, an autonomous agent could initiate transactions that drain accounts or exceed budgets. Intercept blocks financial tools by default, requiring human-in-the-loop approval with configurable spending limits per transaction and per time window.

Financial tools involve real money. Block by default and require explicit human approval before enabling.

merx-tron-resource-exchange.yaml
tools:
  transfer_trx:
    rules:
      - action: deny
        reason: "Requires human approval"

See the full MERX - TRON Resource Exchange policy for all 66 tools.

Tool Name transfer_trx
Category Financial
Risk Level Critical

View all 66 tools →

Agents calling financial-class tools like transfer_trx have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Financial risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

transfer_trx is one of the critical-risk operations in MERX - TRON Resource Exchange. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the transfer_trx tool do? +

Send TRX to an address. Checks bandwidth, buys via Merx if needed. Signs and broadcasts on-chain. Requires TRON_PRIVATE_KEY.. It is categorised as a Financial tool in the MERX - TRON Resource Exchange MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on transfer_trx? +

Add a rule in your Intercept YAML policy under the tools section for transfer_trx. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the MERX - TRON Resource Exchange MCP server.

What risk level is transfer_trx? +

transfer_trx is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit transfer_trx? +

Yes. Add a rate_limit block to the transfer_trx rule in your Intercept 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.

How do I block transfer_trx completely? +

Set action: deny in the Intercept policy for transfer_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.

What MCP server provides transfer_trx? +

transfer_trx is provided by the MERX - TRON Resource Exchange MCP server (merx-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.