AI agents use undelegate_resource to create or update resources in Tron — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tron environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
amount | number | Yes | Amount of resources to revoke in Sun (1 TRX = 1,000,000 Sun) |
network | string | — | Network name. Defaults to mainnet. |
resource | string | Yes | Resource type to revoke (BANDWIDTH or ENERGY) |
receiverAddress | string | Yes | The address from which delegated resources will be revoked |
Parameters from the server's own tool schema.
This tool modifies the delegation state of staked resources on the TRON blockchain by revoking a previously established delegation. It is reversible (resources can be re-delegated) and does not delete data, move funds, or execute arbitrary code. It falls under Write as it updates blockchain state in a reversible manner.
From the tool's definition Revoke previously delegated staked resources (BANDWIDTH or ENERGY) from a receiver address back to the configured wallet
Attacks that exploit this kind of access
Revoke previously delegated staked resources (BANDWIDTH or ENERGY) from a receiver address back to the configured wallet. It is categorised as a Write tool in the Tron MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
undelegate_resource accepts 4 parameters: amount, network, resource, receiverAddress. Required: amount, resource, receiverAddress. 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 undelegate_resource: 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.
undelegate_resource is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the undelegate_resource 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 undelegate_resource. 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.
undelegate_resource 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 →