AI agents use approve_proposal 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 |
|---|---|---|---|
approve | boolean | Yes | true to approve, false to disapprove |
network | string | — | Network name. Defaults to mainnet. |
proposalId | integer | Yes | The proposal ID to vote on |
Parameters from the server's own tool schema.
An AI agent can call approve_proposal faster than any human can review — one bad instruction and it creates or modifies resources in Tron by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Vote to approve or disapprove a governance proposal (SR only). 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.
approve_proposal accepts 3 parameters: approve, network, proposalId. Required: approve, proposalId. 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 approve_proposal: 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.
approve_proposal 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 approve_proposal 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 approve_proposal. 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.
approve_proposal 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 →