Clear the on-chain ABI metadata of a contract (ClearABIContract). Requires the contract creator's wallet.
AI agents call clear_abi 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. |
contractAddress | string | Yes | The contract address whose ABI will be cleared |
Parameters from the server's own tool schema.
Clearing ABI metadata is an irreversible operation that destroys data on the blockchain. Once cleared, the contract's interface specification is lost and cannot be undone without redeployment or re-initialization by the contract creator. This is a destructive action with significant consequences for contract interaction and transparency, warranting 'Destructive' classification.
From the tool's definition Tool description explicitly states 'Clear the on-chain ABI metadata of a contract' — uses the verb 'clear' which indicates irreversible deletion of data. The ABI (Application Binary Interface) is metadata stored on-chain that cannot be restored once deleted.
Attacks that exploit this kind of access
Clear the on-chain ABI metadata of a contract (ClearABIContract). Requires the contract creator's wallet. 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.
clear_abi accepts 2 parameters: network, contractAddress. Required: contractAddress. 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 clear_abi: 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.
clear_abi 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 clear_abi 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 clear_abi. 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.
clear_abi 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 →