AI agents call get_available_unfreeze_count 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. |
Parameters from the server's own tool schema.
This tool retrieves and queries data (the count of available unfreeze operations) from the blockchain without modifying, executing, or destroying any data. It is a pure read operation with no capability to alter state or commit financial transactions. Low severity as the information retrieved cannot harm the system even if misused.
From the tool's definition Tool name contains 'get_' prefix and description uses 'Get' verb indicating a query operation. Returns 'remaining available unstake operations' count for an address with no side effects mentioned.
Attacks that exploit this kind of access
Get remaining available unstake (unfreeze) operations for an address 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_available_unfreeze_count accepts 2 parameters: address, network. 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_available_unfreeze_count: 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_available_unfreeze_count 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_available_unfreeze_count 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_available_unfreeze_count. 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_available_unfreeze_count 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 →