prepare_tron_lifi_swap

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Critical RISK CLASS

Category Financial

Parameters 76 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/prepare-tron-lifi-swap.md

WHAT IT DOES

What prepare_tron_lifi_swap does on VaultPilot MCP

AI agents use prepare_tron_lifi_swap to commit financial operations through VaultPilot MCP, usually the final step of a payment, billing, or trading workflow. A call moves real money.

Parameter	Type	Required	Description
`wallet`	string	Yes	TRON base58 wallet (T-prefixed, 34 chars) — funds the swap and signs the source tx on Ledger via USB. Pair via `pair_ledger_tron` first.
`toChain`	string	Yes	Destination chain. Any EVM chain (cross-chain bridge to EVM) or "solana" (cross-chain bridge to Solana). LiFi internally picks the best bridge protocol (NearInt
`toToken`	string	Yes	Destination token. 0x-prefixed EVM token when toChain is EVM; SPL mint base58 when toChain="solana". "native" works on both (resolves to the chain's conventiona
`fromToken`	string	Yes	Source token. T-prefixed TRC-20 contract address OR the literal string "native" for TRX (LiFi maps "native" to TRX's contract address internally). TRC-20 source
`toAddress`	string	Yes	Destination wallet — REQUIRED. EVM hex when toChain is EVM; Solana base58 when toChain="solana". The TRON source wallet isn't a valid recipient on either destin
`fromAmount`	string	Yes	Raw integer amount in base units (NOT decimal-adjusted). For TRX (6 decimals) 1 TRX = '1000000'; for TRC-20 USDT (6 decimals) 10 USDT = '10000000'.
`slippageBps`	integer	—	Slippage tolerance in basis points (50 = 0.5%). Omit for LiFi's default (0.5%). Cross-chain bridges may impose their own minimums above this.

Parameters from the server's own tool schema.

RISK

Why prepare_tron_lifi_swap is rated Critical

This tool builds a transaction that moves crypto tokens across chains via a bridge protocol. Even though it only prepares/builds an unsigned transaction, it is a direct precursor to financial asset movement (bridging tokens from TRON to EVM/Solana chains). The Financial category applies because it commits to moving financial assets, and misuse could result in loss of funds.

From the tool's definition cross-chain bridge...bridge protocol delivers tokens on the destination...LiFi aggregates NearIntents, Wormhole, Allbridge...TriggerSmartContract envelope...BridgeData tuple

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs prepare_tron_lifi_swap safely

PolicyLayer is an MCP gateway: it sits between your AI agents and VaultPilot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For prepare_tron_lifi_swap, this is the rule to start with:

prepare_tron_lifi_swap Approval-gated

Any call to prepare_tron_lifi_swap is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "prepare_tron_lifi_swap": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect VaultPilot MCP, apply this rule, and every prepare_tron_lifi_swap call is checked against it from then on.

FAQ

Questions about prepare_tron_lifi_swap

What does the prepare_tron_lifi_swap tool do? +

Build an unsigned LiFi-routed cross-chain bridge with TRON as the source chain. User signs a TRON tx via Ledger over USB; the bridge protocol delivers tokens on the destination (any EVM chain or Solana) after the source confirms (typically 1-15 min). LiFi aggregates NearIntents, Wormhole, Allbridge, etc. The builder (1) decodes the TRON protobuf to extract the TriggerSmartContract envelope, (2) asserts the contract_address is the LiFi Diamond on TRON (TU3ymitEKCWQFtASkEeHaPb8NfZcJtCHLt) and the owner_address is the user's wallet, (3) decodes the inner ABI calldata's BridgeData tuple and cross-checks destinationChainId + receiver against the user's request — refuses on any mismatch. NEAR Intents routes (intermediate-chain settlement on NEAR's pseudo-chain 1885080386571452) are allowlisted via a hardcoded source-code constant so a hostile aggregator cannot fabricate 'intermediate-chain' encodings; receiver-side checks still apply unchanged. TRC-20 source flows REQUIRE a prior approve to the LiFi Diamond — call prepare_tron_trc20_approve first with spender: "TU3ymitEKCWQFtASkEeHaPb8NfZcJtCHLt" and the amount you intend to swap; insufficient allowance reverts the swap on-chain. BLIND-SIGN on Ledger (LiFi Diamond not in TRON app's clear-sign allowlist) — enable "Allow blind signing" in the on-device Solana app Settings; the device shows the txID, which the user matches against the txID in the prepare receipt. Pair the Ledger via pair_ledger_tron first. Broadcast goes via TronGrid's /wallet/broadcasthex endpoint (LiFi gives us only raw_data_hex, not the deserialized JSON shape /wallet/broadcasttransaction requires). It is categorised as a Financial tool in the VaultPilot MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does prepare_tron_lifi_swap accept? +

prepare_tron_lifi_swap accepts 7 parameters: wallet, toChain, toToken, fromToken, toAddress, fromAmount, slippageBps. Required: wallet, toChain, toToken, fromToken, toAddress, fromAmount. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on prepare_tron_lifi_swap? +

Register the VaultPilot MCP server in PolicyLayer and add a rule for prepare_tron_lifi_swap: 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 VaultPilot MCP. Nothing to install.

What risk level is prepare_tron_lifi_swap? +

prepare_tron_lifi_swap 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 prepare_tron_lifi_swap? +

Yes. Add a rate_limit block to the prepare_tron_lifi_swap 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.

How do I block prepare_tron_lifi_swap completely? +

Set action: deny in the PolicyLayer policy for prepare_tron_lifi_swap. 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 prepare_tron_lifi_swap? +

prepare_tron_lifi_swap is provided by the VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on VaultPilot, and thousands of servers like it.

This server

All 189 VaultPilot tools → Critical-risk tools on this server →

Across the catalogue

menese_swap on Mcp Menesesdk → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →