AI agents call get_trx_price 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 public market data (TRX cryptocurrency price) from CoinGecko. It is a read-only operation with no side effects, no code execution, and no data modification. The blast radius is minimal—worst case, an AI agent misuses the price data in downstream logic, but the tool itself cannot cause harm. Low severity reflects the informational nature and lack of destructive potential.
From the tool's definition Tool name 'get_trx_price' and description 'Get current TRX price from CoinGecko' indicate a query operation that retrieves real-time price data from an external API without modifying or executing state-changing operations.
Attacks that exploit this kind of access
Get current TRX price from CoinGecko. 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_trx_price: 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_trx_price 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_trx_price 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_trx_price. 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_trx_price 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 →