Build an unsigned TRON Stake 2.0 FreezeBalanceV2 transaction. Locks TRX to earn bandwidth (fuels plain transfers) or energy (fuels smart-contract calls) and gains proportional voting power. IMPORTANT: freezing alone does NOT accrue TRX rewards — claimableRewards (see get_tron_staking) only grows ...
AI agents invoke prepare_tron_freeze to trigger actions in VaultPilot MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
from | string | Yes | Base58 TRON owner address (prefix T). |
amount | string | Yes | TRX amount to freeze as a human-readable decimal string (converted to SUN internally). |
resource | string | Yes | Which Stake 2.0 resource to freeze/unfreeze TRX for. `bandwidth` fuels plain transactions; `energy` fuels smart-contract calls. |
Parameters from the server's own tool schema.
prepare_tron_freeze triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
Build an unsigned TRON Stake 2.0 FreezeBalanceV2 transaction. Locks TRX to earn bandwidth (fuels plain transfers) or energy (fuels smart-contract calls) and gains proportional voting power. IMPORTANT: freezing alone does NOT accrue TRX rewards — claimableRewards (see get_tron_staking) only grows after the user also votes for a Super Representative. Pair this tool with list_tron_witnesses + prepare_tron_vote for the full reward-earning flow. Unlocking requires a 14-day cooldown via prepare_tron_unfreeze + prepare_tron_withdraw_expire_unfreeze. Returns a preview + opaque handle; forward via send_transaction for USB-HID signing on the paired Ledger. It is categorised as a Execute tool in the VaultPilot MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
prepare_tron_freeze accepts 3 parameters: from, amount, resource. Required: from, amount, resource. The full parameter table on this page comes from the server's own tool schema.
Register the VaultPilot MCP server in PolicyLayer and add a rule for prepare_tron_freeze: 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.
prepare_tron_freeze is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the prepare_tron_freeze 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 prepare_tron_freeze. 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.
prepare_tron_freeze 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.