AI agents call get_can_withdraw_unfreeze_amount to retrieve information from Tron without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
address | string | Yes | Wallet address (Base58 or hex) |
network | string | — | Network name. Defaults to mainnet. |
timestampMs | string | — | Optional query timestamp in milliseconds. Defaults to current time. |
Parameters from the server's own tool schema.
This tool only reads blockchain state to determine how much TRX an address can withdraw from an unstaking pool. It has no side effects, does not move funds, and does not execute transactions. The query is purely informational.
From the tool's definition Tool name contains 'get_' and description states 'Get the withdrawable unstaked TRX amount' — this is a query operation that retrieves data about an address's unstaking status without modifying state or executing transactions.
Attacks that exploit this kind of access
Get the withdrawable unstaked TRX amount for an address at a given timestamp in Stake 2.0. It is categorised as a Read tool in the Tron MCP Server, which means it retrieves data without modifying state.
get_can_withdraw_unfreeze_amount accepts 3 parameters: address, network, timestampMs. Required: address. The full parameter table on this page comes from the server's own tool schema.
Register the Tron MCP server in PolicyLayer and add a rule for get_can_withdraw_unfreeze_amount: 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 Tron. Nothing to install.
get_can_withdraw_unfreeze_amount is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_can_withdraw_unfreeze_amount 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 get_can_withdraw_unfreeze_amount. 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.
get_can_withdraw_unfreeze_amount is provided by the Tron MCP server (@bankofai/mcp-server-tron). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →