Get transaction history for a smart contract from TronGrid indexed data. Unlike get_account_transactions, this aggregates transactions BY contract. Supports pagination via limit + fingerprint. Default 20 results, max 200 per page.
AI agents call get_contract_transactions 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 |
|---|---|---|---|
limit | number | — | Max transactions per page (default 20, max 200) |
address | string | Yes | Contract address (base58 T-address or hex 41-prefixed) |
network | string | — | Network name. Defaults to mainnet. |
orderBy | string | — | Sort field, e.g. 'block_timestamp,desc' |
fingerprint | string | — | Pagination token from previous response |
maxTimestamp | number | — | Filter: maximum block timestamp (ms) |
minTimestamp | number | — | Filter: minimum block timestamp (ms) |
onlyConfirmed | boolean | — | Only return confirmed transactions |
onlyUnconfirmed | boolean | — | Only return unconfirmed transactions |
Parameters from the server's own tool schema.
This tool retrieves historical transaction data from TronGrid indexed data without any side effects. It is a pure query operation that fetches and presents existing blockchain data. The severity is low because querying transaction history poses minimal risk—the data is already public on the blockchain and the operation cannot modify state or trigger financial transactions.
From the tool's definition Tool description explicitly states 'Get transaction history' and 'aggregates transactions BY contract', with no mention of modifying, executing, or deleting data. Pagination parameters (limit, fingerprint) are characteristic of read-only query operations.
Attacks that exploit this kind of access
Get transaction history for a smart contract from TronGrid indexed data. Unlike get_account_transactions, this aggregates transactions BY contract. Supports pagination via limit + fingerprint. Default 20 results, max 200 per page. It is categorised as a Read tool in the Tron MCP Server, which means it retrieves data without modifying state.
get_contract_transactions accepts 9 parameters: limit, address, network, orderBy, fingerprint, maxTimestamp, minTimestamp, onlyConfirmed, onlyUnconfirmed. Required: address. 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 get_contract_transactions: 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.
get_contract_transactions 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 get_contract_transactions 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 get_contract_transactions. 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.
get_contract_transactions 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 →