AI agents call get_events_by_contract_address 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 events per page (default 20, max 200) |
network | string | — | Network name. Defaults to mainnet. |
orderBy | string | — | Sort order |
eventName | string | — | Filter by event name (e.g. Transfer) |
fingerprint | string | — | Pagination token from previous response |
onlyConfirmed | boolean | — | Only return confirmed events |
contractAddress | string | Yes | The contract address (base58 or hex) |
Parameters from the server's own tool schema.
This tool queries blockchain event logs for a given contract address. It retrieves historical data without side effects, state changes, or triggering any transactions. It is purely informational and carries minimal risk even if misused by an AI agent, as it cannot alter blockchain state or execute code.
From the tool's definition Tool name and description indicate retrieval of data: 'Get recent events emitted by a specific contract address.' The verb 'Get' and the passive construction 'events emitted' describe a read-only query operation with no modification, execution, or financial…
Attacks that exploit this kind of access
Get recent events emitted by a specific contract address. It is categorised as a Read tool in the Tron MCP Server, which means it retrieves data without modifying state.
get_events_by_contract_address accepts 7 parameters: limit, network, orderBy, eventName, fingerprint, onlyConfirmed, 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 get_events_by_contract_address: 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_events_by_contract_address 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_events_by_contract_address 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_events_by_contract_address. 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_events_by_contract_address 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 →