AI agents use update_contract_setting 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 |
consumeUserResourcePercent | number | Yes | New consume_user_resource_percent value (0-100) |
Parameters from the server's own tool schema.
This tool modifies contract configuration settings on the TRON blockchain. While it changes contract state, the update is reversible (can be changed back), so it is categorized as Write rather than Execute or Destructive.
From the tool's definition Tool description states 'Update a contract's consume_user_resource_percent' and 'Requires the contract creator's wallet.' This modifies contract state (the user pay ratio setting) in a reversible manner.
Attacks that exploit this kind of access
Update a contract's consume_user_resource_percent (user pay ratio). 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_contract_setting accepts 3 parameters: network, contractAddress, consumeUserResourcePercent. Required: contractAddress, consumeUserResourcePercent. 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_contract_setting: 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_contract_setting 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_contract_setting 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_contract_setting. 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_contract_setting 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 →