Gets currently trending tokens from CoinGecko.
AI agents call get_trending_tokens to retrieve information from SEI MCP Server V2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries external data (CoinGecko API) and returns information about trending tokens. It performs no modifications, deletions, financial transactions, or code execution. It is a straightforward data retrieval operation with no blast radius if misused by an AI agent—the worst outcome would be receiving stale or irrelevant market information.
From the tool's definition Tool name 'get_trending_tokens' and description 'Gets currently trending tokens from CoinGecko' indicate retrieval of public market data with no side effects.
Attacks that exploit this kind of access
Gets currently trending tokens from CoinGecko. It is categorised as a Read tool in the SEI MCP Server V2 MCP Server, which means it retrieves data without modifying state.
Register the SEI MCP Server V2 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 SEI MCP Server V2. 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 SEI MCP Server V2 MCP server (testinguser1111111/sei-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 →