AI agents invoke deploy_contract to trigger actions in Tron. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
abi | array | Yes | The contract ABI (array of objects) |
args | array | — | Constructor arguments |
name | string | — | Contract name (optional) |
network | string | — | Network name. Defaults to mainnet. |
bytecode | string | Yes | The compiled contract bytecode (hex string) |
feeLimit | number | — | Fee limit in Sun (default: 1,000,000,000 = 1000 TRX) |
Parameters from the server's own tool schema.
This tool executes code (smart contract bytecode) on the TRON blockchain. While not immediately destructive (contracts can be deployed without data loss), smart contract execution is irreversible in practice and can trigger arbitrary state changes, financial transfers, or other uncontrolled effects depending on contract code.
From the tool's definition Deploy a smart contract to the TRON network using ABI and Bytecode. Smart contract deployment is code execution on a blockchain that creates permanent, autonomous programs with potentially significant side effects (state changes, fund transfers, or…
Attacks that exploit this kind of access
Deploy a smart contract to the TRON network using ABI and Bytecode. It is categorised as a Execute tool in the Tron MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
deploy_contract accepts 6 parameters: abi, args, name, network, bytecode, feeLimit. Required: abi, bytecode. 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 deploy_contract: 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.
deploy_contract is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the deploy_contract 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 deploy_contract. 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.
deploy_contract 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 →