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

prepare_tron_claim_rewards

Build an unsigned TRON WithdrawBalance transaction that claims accumulated voting rewards to the owner's balance. TRON enforces a 24-hour cooldown between claims — TronGrid will reject (surfaced as an error) if the previous claim was inside the window. Pair with get_tron_staking first to read cla...

SERVERVaultPilot MCP SOURCEvaultpilot-mcp
Critical RISK CLASS
Category Financial
Parameters 11 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-claim-rewards.md

What prepare_tron_claim_rewards does on VaultPilot MCP

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

ParameterTypeRequiredDescription
from string Yes Base58 TRON address to claim accumulated voting rewards for. TRON enforces a 24h cooldown between claims.

Parameters from the server's own tool schema.

Why prepare_tron_claim_rewards is rated Critical

This tool builds and prepares a financial transaction on the TRON blockchain that claims accumulated staking/voting rewards. While it only builds an unsigned transaction (the actual signing and broadcast happen via `send_transaction`), it directly initiates a financial operation involving crypto asset movement.

From the tool's definition 'claims accumulated voting rewards to the owner's balance' and 'forward via `send_transaction` for USB-HID signing' — initiates a TRON blockchain transaction that moves crypto assets (rewards) into an account

Questions about prepare_tron_claim_rewards

What does the prepare_tron_claim_rewards tool do? +

Build an unsigned TRON WithdrawBalance transaction that claims accumulated voting rewards to the owner's balance. TRON enforces a 24-hour cooldown between claims — TronGrid will reject (surfaced as an error) if the previous claim was inside the window. Pair with get_tron_staking first to read claimableRewards and avoid empty-claim tx builds. 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.

What parameters does prepare_tron_claim_rewards accept? +

prepare_tron_claim_rewards accepts 1 parameter: from. Required: from. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on prepare_tron_claim_rewards? +

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

prepare_tron_claim_rewards 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_claim_rewards? +

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

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

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