List currently trending tokens across Relay-supported chains. Returns token identities only (symbol, name, address, chainId) — NOT prices or volumes. To get pricing for a trending token, follow up with get_token_price or get_token_details. Use this to answer
AI agents call get_trending_tokens to retrieve information from Relay MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query to retrieve metadata about trending tokens across blockchain networks. It returns informational data only (identifiers like symbol, name, address, chainId) without enabling any transactions, state modifications, or financial operations. The severity is low because misuse would only expose harmless trending token information with no blast radius or security impact.
From the tool's definition Tool returns 'token identities only (symbol, name, address, chainId) — NOT prices or volumes.' It is explicitly described as a retrieval operation that 'List[s] currently trending tokens' with no side effects or state changes.
Attacks that exploit this kind of access
List currently trending tokens across Relay-supported chains. Returns token identities only (symbol, name, address, chainId) — NOT prices or volumes. To get pricing for a trending token, follow up with get_token_price or get_token_details. Use this to answer. It is categorised as a Read tool in the Relay MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Relay MCP Server MCP server in PolicyLayer and add a rule for get_trending_tokens: 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 Relay MCP Server. Nothing to install.
get_trending_tokens 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_trending_tokens 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_trending_tokens. 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_trending_tokens is provided by the Relay MCP Server MCP server (relayprotocol/relay-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 →