get_tron_staking

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What get_tron_staking does on VaultPilot MCP

AI agents call get_tron_staking to retrieve information from VaultPilot MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`address`	string	Yes	Base58 TRON mainnet address (prefix T) — the wallet to read staking state for.

Parameters from the server's own tool schema.

RISK

Why get_tron_staking is rated Low

This tool retrieves and displays staking state information for a given TRON address without modifying any data or triggering transactions. It is purely informational/querying in nature, making it a Read category tool with low severity since misuse would only expose data visibility rather than enable harmful actions.

From the tool's definition Tool name includes 'get_' prefix and description explicitly states 'Read TRON staking state' with emphasis on querying and displaying data: 'claimable voting rewards', 'frozen TRX', 'pending unfreezes', 'account-resource meter', 'per-SR vote allocation'.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_tron_staking Allowed

get_tron_staking is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_tron_staking": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect VaultPilot MCP, apply this rule, and every get_tron_staking call is checked against it from then on.

FAQ

Questions about get_tron_staking

What does the get_tron_staking tool do? +

Read TRON staking state for a base58 address: claimable voting rewards (WithdrawBalance-ready), frozen TRX under Stake 2.0 (bandwidth + energy), pending unfreezes with unlock timestamps, the live account-resource meter (resources) showing immediately-consumable bandwidth units (free + staked pools), energy units, and voting-power units, AND the per-SR vote allocation (votes[] — same shape as list_tron_witnesses(addr).userVotes, issue #271). The resource meter is what tx execution actually charges against — frozen TRX only determines the daily limit. The votes[] baseline is what callers building prepare_tron_vote rebalances need: VoteWitness REPLACES the entire allocation, so consolidating onto an existing SR or rebalancing freshly-unlocked TRON Power requires the current breakdown — this field provides it without forcing a chained list_tron_witnesses call. Read-only; pair with prepare_tron_claim_rewards to withdraw rewards or prepare_tron_vote to allocate voting power. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.

What parameters does get_tron_staking accept? +

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

How do I enforce a policy on get_tron_staking? +

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

get_tron_staking is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_tron_staking? +

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

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

get_tron_staking 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 →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →