Build an unsigned TRON WithdrawExpireUnfreeze transaction — sweeps every matured unfreeze slice (those whose 14-day cooldown elapsed) back to liquid TRX. No amount needed; the chain drains all eligible slices in one call. Inspect pendingUnfreezes from get_tron_staking first — if every entry's unl...
AI agents use prepare_tron_withdraw_expire_unfreeze 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 |
|---|---|---|---|
from | string | Yes | Base58 TRON owner address. Sweeps all unfreezes whose 14-day cooldown has elapsed (see `pendingUnfreezes[].unlockAt` from `get_tron_staking`) back to liquid TRX |
Parameters from the server's own tool schema.
prepare_tron_withdraw_expire_unfreeze moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Build an unsigned TRON WithdrawExpireUnfreeze transaction — sweeps every matured unfreeze slice (those whose 14-day cooldown elapsed) back to liquid TRX. No amount needed; the chain drains all eligible slices in one call. Inspect pendingUnfreezes from get_tron_staking first — if every entry's unlockAt is still in the future, TronGrid returns 'no expire unfreeze' and this tool errors. Returns a preview + opaque handle; forward via send_transaction for USB-HID signing on the paired Ledger. 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.
prepare_tron_withdraw_expire_unfreeze accepts 1 parameter: from. Required: from. 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_withdraw_expire_unfreeze: 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_withdraw_expire_unfreeze 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 prepare_tron_withdraw_expire_unfreeze 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_withdraw_expire_unfreeze. 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_withdraw_expire_unfreeze 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.