AI agents call get_trongrid_account 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.
This tool retrieves account information from the TronGrid API, which is a query operation with no side effects. It does not create, modify, delete, or execute transactions. The severity is low because account information queries pose minimal risk—they are public blockchain data with no capability to alter state or commit financial transactions.
From the tool's definition Tool name 'get_trongrid_account' and description 'Get account information directly from TronGrid API' indicate data retrieval without modification. The verb 'Get' and the context of querying blockchain account information confirm read-only operations.
Attacks that exploit this kind of access
Get account information directly from TronGrid API. It is categorised as a Read tool in the Tron MCP Server, which means it retrieves data without modifying state.
Register the Tron MCP server in PolicyLayer and add a rule for get_trongrid_account: 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_trongrid_account 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_trongrid_account 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_trongrid_account. 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_trongrid_account is provided by the Tron MCP server (netts-official/tron_mcp_server). 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 →