Delete a governance proposal (SR only, only the proposal creator can delete it).
AI agents call delete_proposal to permanently remove resources in Tron — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
network | string | — | Network name. Defaults to mainnet. |
proposalId | integer | Yes | The proposal ID to delete |
Parameters from the server's own tool schema.
This tool permanently removes a governance proposal, which is an irreversible destructive operation. Although restricted to proposal creators (SR), if an AI agent obtains the necessary permissions or credentials, it could delete important proposals, disrupting blockchain governance. The high severity reflects the governance impact, though the access control somewhat mitigates the blast radius.
From the tool's definition Tool name explicitly includes 'delete' and description states it will 'Delete a governance proposal'. This is an irreversible action that removes governance data from the blockchain.
Attacks that exploit this kind of access
Delete a governance proposal (SR only, only the proposal creator can delete it). It is categorised as a Destructive tool in the Tron MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_proposal accepts 2 parameters: network, proposalId. Required: 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 delete_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.
delete_proposal is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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 →