AI agents use account_permission_update 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. |
ownerPermission | object | Yes | Owner permission configuration |
activePermissions | object | Yes | Active permission(s) configuration |
witnessPermission | object | — | Witness permission (only for Super Representatives) |
Parameters from the server's own tool schema.
This tool modifies account permissions on the TRON blockchain, which is a write operation that changes access control settings. While reversible in principle (permissions can be updated again), misconfiguration could effectively lock out the account owner or grant unauthorized parties control over the account, making the blast radius high.
From the tool's definition Update account permissions for multi-signature configuration. Set owner, active, and optional witness permissions.
Risk signalsHigh parameter count (16 properties)
Attacks that exploit this kind of access
Update account permissions for multi-signature configuration. Set owner, active, and optional witness permissions. 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.
account_permission_update accepts 4 parameters: network, ownerPermission, activePermissions, witnessPermission. Required: ownerPermission, activePermissions. 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 account_permission_update: 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.
account_permission_update 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 account_permission_update 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 account_permission_update. 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.
account_permission_update 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 →