get_recent_pumpfun_graduates
AI agents call get_recent_pumpfun_graduates 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 retrieves information about recent Pump.fun token graduates—a read-only query operation with no side effects. It observes market data without modifying, deleting, or executing code. While the memecoin space carries financial risks, the tool itself is non-destructive. Confidence is slightly reduced (0.85 vs. higher) due to the empty description, which prevents direct confirmation of its exact behavior.
From the tool's definition Tool name 'get_recent_pumpfun_graduates' indicates a retrieval operation ('get'), and the server's stated purpose is 'Real-time radar' for token monitoring.
Attacks that exploit this kind of access
get_recent_pumpfun_graduates. 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_recent_pumpfun_graduates: 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_recent_pumpfun_graduates 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_recent_pumpfun_graduates 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_recent_pumpfun_graduates. 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_recent_pumpfun_graduates 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 →