New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

prepare_tron_unfreeze

Build an unsigned TRON Stake 2.0 UnfreezeBalanceV2 transaction — begins the 14-day cooldown on a previously-frozen slice. The amount must not exceed what's currently frozen for that resource (query get_tron_staking first; TronGrid rejects otherwise with 'less than frozen balance'). After 14 days ...

SERVERVaultPilot MCP SOURCEvaultpilot-mcp
High RISK CLASS
Category Execute
Parameters 33 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

What prepare_tron_unfreeze does on VaultPilot MCP

AI agents invoke prepare_tron_unfreeze 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.

ParameterTypeRequiredDescription
from string Yes Base58 TRON owner address (prefix T).
amount string Yes TRX amount to unfreeze. Must not exceed the currently-frozen amount for the given resource — TronGrid rejects otherwise.
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.

Why prepare_tron_unfreeze is rated High

This tool triggers an irreversible state change on a blockchain (initiating unfreezing of staked assets) that cannot be undone within the 14-day window and commits the user to a specific financial timeline.

From the tool's definition Tool builds and initiates a TRON Stake 2.0 UnfreezeBalanceV2 transaction that begins a 14-day cooldown on frozen assets.

Questions about prepare_tron_unfreeze

What does the prepare_tron_unfreeze tool do? +

Build an unsigned TRON Stake 2.0 UnfreezeBalanceV2 transaction — begins the 14-day cooldown on a previously-frozen slice. The amount must not exceed what's currently frozen for that resource (query get_tron_staking first; TronGrid rejects otherwise with 'less than frozen balance'). After 14 days the slice shows up in pendingUnfreezes with an elapsed unlockAt; call prepare_tron_withdraw_expire_unfreeze to sweep it back to liquid TRX. 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.

What parameters does prepare_tron_unfreeze accept? +

prepare_tron_unfreeze 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.

How do I enforce a policy on prepare_tron_unfreeze? +

Register the VaultPilot MCP server in PolicyLayer and add a rule for prepare_tron_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.

What risk level is prepare_tron_unfreeze? +

prepare_tron_unfreeze is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit prepare_tron_unfreeze? +

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

How do I block prepare_tron_unfreeze completely? +

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

What MCP server provides prepare_tron_unfreeze? +

prepare_tron_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.

More on VaultPilot, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of VaultPilot's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.