get_trending_tokens_by_kol_trading_volume
AI agents call get_trending_tokens_by_kol_trading_volume to retrieve information from Memecoin Radar without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns data about token trends and KOL trading activity. The 'get_' prefix and pattern match other read-only retrieval tools on the same server. There is no indication of write, execute, destructive, or financial operations. The slightly reduced confidence (0.85 vs.
From the tool's definition Tool name indicates it retrieves trending tokens filtered by KOL trading volume metrics. The empty description provides no contradictory evidence.
Attacks that exploit this kind of access
get_trending_tokens_by_kol_trading_volume. It is categorised as a Read tool in the Memecoin Radar MCP Server, which means it retrieves data without modifying state.
Register the Memecoin Radar MCP server in PolicyLayer and add a rule for get_trending_tokens_by_kol_trading_volume: 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 Memecoin Radar. Nothing to install.
get_trending_tokens_by_kol_trading_volume 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_by_kol_trading_volume 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_by_kol_trading_volume. 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_by_kol_trading_volume is provided by the Memecoin Radar MCP server (kukapay/memecoin-radar-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 →