Alias to /v2/aggregations/trending-tokens (timeframe, chain, limit, cursor).
AI agents call elfa_trending to retrieve information from CG Alpha MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches read-only aggregated market data about trending tokens. It has no side effects, does not modify any data, and only queries an endpoint for token trend information. The severity is low as misuse would at most expose market data without any financial, destructive, or execution risk.
From the tool's definition Alias to /v2/aggregations/trending-tokens — retrieves aggregated trending token data with query parameters (timeframe, chain, limit, cursor)
Attacks that exploit this kind of access
Alias to /v2/aggregations/trending-tokens (timeframe, chain, limit, cursor). It is categorised as a Read tool in the CG Alpha MCP MCP Server, which means it retrieves data without modifying state.
Register the CG Alpha MCP server in PolicyLayer and add a rule for elfa_trending: 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 CG Alpha MCP. Nothing to install.
elfa_trending 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 elfa_trending 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 elfa_trending. 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.
elfa_trending is provided by the CG Alpha MCP server (jcf0/cg-alpha-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 →