prepare_tron_native_send

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Critical RISK CLASS

Category Financial

Parameters 33 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-native-send.md

WHAT IT DOES

What prepare_tron_native_send does on VaultPilot MCP

AI agents use prepare_tron_native_send 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
`to`	string	Yes	Base58 TRON recipient address (prefix T).
`from`	string	Yes	Base58 TRON sender address (prefix T).
`amount`	string	Yes	TRX amount as a human-readable decimal string (e.g. "12.5").

Parameters from the server's own tool schema.

RISK

Why prepare_tron_native_send is rated Critical

This tool builds a transaction that, when forwarded to send_transaction, moves TRX (a cryptocurrency with real financial value) on the TRON blockchain. Even though this step only prepares an unsigned transaction, it is the first step in an irreversible financial transfer pipeline.

From the tool's definition 'Build an unsigned TRON native TRX send transaction' and 'Forward the handle via `send_transaction` to sign... and broadcast to TronGrid' — this tool initiates a cryptocurrency transfer of TRX on the TRON network

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs prepare_tron_native_send 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_native_send, this is the rule to start with:

prepare_tron_native_send Approval-gated

Any call to prepare_tron_native_send 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_native_send": {
      "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_native_send call is checked against it from then on.

FAQ

Questions about prepare_tron_native_send

What does the prepare_tron_native_send tool do? +

Build an unsigned TRON native TRX send transaction via TronGrid's /wallet/createtransaction. Returns a human-readable preview + opaque handle. Forward the handle via send_transaction to sign on the directly-connected Ledger (USB HID via @ledgerhq/hw-app-trx) and broadcast to TronGrid. Run pair_ledger_tron once per session first so the TRON app is open and the device address is verified. 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_native_send accept? +

prepare_tron_native_send accepts 3 parameters: to, from, amount. Required: to, from, amount. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on prepare_tron_native_send? +

Register the VaultPilot MCP server in PolicyLayer and add a rule for prepare_tron_native_send: 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_native_send? +

prepare_tron_native_send 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_native_send? +

Yes. Add a rate_limit block to the prepare_tron_native_send 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_native_send completely? +

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

prepare_tron_native_send 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_send on Mcp Menesesdk → All critical-risk MCP tools → The MCP Attack Database →

Guides

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