AI agents call get_can_delegated_max_size 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. |
resource | string | Yes | Resource type to query (BANDWIDTH or ENERGY) |
Parameters from the server's own tool schema.
This tool queries blockchain state to determine resource delegation capacity. It performs no side effects, executes no code, transfers no funds, and modifies no data. It is a pure information retrieval operation, fitting the 'Read' category with low severity since misuse would only expose publicly available blockchain data.
From the tool's definition Tool name 'get_can_delegated_max_size' and description 'Get the maximum amount of TRX (in Sun) that an address can currently delegate' indicates a read-only query operation that retrieves state information without modification or execution.
Attacks that exploit this kind of access
Get the maximum amount of TRX (in Sun) that an address can currently delegate as resources (BANDWIDTH or ENERGY) under 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_delegated_max_size accepts 3 parameters: address, network, resource. Required: address, resource. 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_delegated_max_size: 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_delegated_max_size 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_delegated_max_size 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_delegated_max_size. 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_delegated_max_size 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 →