AI agents call read_contract to retrieve information from Tron without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
abi | array | — | Optional contract ABI array. If not provided, will fetch from chain. Use for contracts with incomplete on-chain ABI. |
args | array | — | Function arguments (supports arrays and objects for complex types) |
network | string | — | Network name. Defaults to mainnet. |
functionName | string | Yes | Function name (e.g., 'name', 'symbol', 'balanceOf') |
contractAddress | string | Yes | The contract address |
Parameters from the server's own tool schema.
This tool retrieves data from smart contracts without modifying state or triggering any state changes. It is purely informational, analogous to querying a database. No financial transactions, code execution, or data modifications are performed.
From the tool's definition Tool name 'read_contract' and description explicitly states 'Call read-only functions on a smart contract.' Read-only operations have no side effects.
Attacks that exploit this kind of access
Call read-only functions on a smart contract. It is categorised as a Read tool in the Tron MCP Server, which means it retrieves data without modifying state.
read_contract accepts 5 parameters: abi, args, network, functionName, contractAddress. Required: functionName, 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 read_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.
read_contract is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the read_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 read_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.
read_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 →