Get TRC-20 token metadata: name, symbol, decimals, total supply. No auth required.
AI agents call get_token_info to retrieve information from MERX - TRON Resource Exchange without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and queries immutable metadata about tokens on the TRON blockchain. It performs no writes, executions, deletions, or financial transactions. The low severity reflects minimal blast radius even if misused—an AI agent querying token metadata cannot cause harm beyond information gathering.
From the tool's definition Tool description explicitly states it retrieves 'TRC-20 token metadata: name, symbol, decimals, total supply' with 'No auth required.' These are read-only queries of public blockchain data with no side effects.
Attacks that exploit this kind of access
Get TRC-20 token metadata: name, symbol, decimals, total supply. No auth required. It is categorised as a Read tool in the MERX - TRON Resource Exchange MCP Server, which means it retrieves data without modifying state.
Register the MERX - TRON Resource Exchange MCP server in PolicyLayer and add a rule for get_token_info: 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 MERX - TRON Resource Exchange. Nothing to install.
get_token_info 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_token_info 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_token_info. 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_token_info is provided by the MERX - TRON Resource Exchange MCP server (Hovsteder/merx-mcp). 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 →