AI agents use update_energy_limit 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 |
|---|---|---|---|
network | string | — | Network name. Defaults to mainnet. |
contractAddress | string | Yes | The contract address |
originEnergyLimit | number | Yes | New originEnergyLimit value (energy units, must be > 0) |
Parameters from the server's own tool schema.
This tool modifies contract parameters (originEnergyLimit) on the TRON blockchain, making it a Write operation rather than Read (which would only query) or Destructive (which would irreversibly delete).
From the tool's definition Tool description states it 'Update[s] a contract's originEnergyLimit', which is a modification operation. The requirement for 'the contract creator's wallet' indicates authentication/authorization is needed.
Attacks that exploit this kind of access
Update a contract's originEnergyLimit (max energy the contract creator will pay per execution). Requires the contract creator's 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.
update_energy_limit accepts 3 parameters: network, contractAddress, originEnergyLimit. Required: contractAddress, originEnergyLimit. 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 update_energy_limit: 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.
update_energy_limit 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 update_energy_limit 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 update_energy_limit. 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.
update_energy_limit 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 →