AI agents call get_approved_list 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 |
|---|---|---|---|
network | string | — | Network name. Defaults to mainnet. |
transaction | string | Yes | The full signed transaction as a JSON string |
Parameters from the server's own tool schema.
This tool queries and retrieves information about transaction signatures—a data retrieval operation with no side effects. It does not create, modify, delete, or execute any blockchain state changes. While it's part of a blockchain server with financial implications, the tool itself only reads approval/signature data, making it a Read category risk.
From the tool's definition Tool name 'get_approved_list' and description 'Query the list of accounts that have signed a given transaction' indicate a read-only operation that retrieves data without modifying state or executing actions.
Attacks that exploit this kind of access
Query the list of accounts that have signed a given transaction. Pass the full transaction JSON object. It is categorised as a Read tool in the Tron MCP Server, which means it retrieves data without modifying state.
get_approved_list accepts 2 parameters: network, transaction. Required: transaction. 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_approved_list: 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_approved_list 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_approved_list 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_approved_list. 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_approved_list 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 →