get_trading_wallets
AI agents call get_trading_wallets to retrieve information from Pumpfun Wallets without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve or list trading wallet information from the Pump.fun/PumpSwap blockchain analysis system. There is no evidence of write, execute, destructive, or financial operations—it is a query/lookup function. The empty description slightly reduces confidence, but the consistent naming pattern with other read-only sibling tools and the server's analytical purpose confirm a Read classification.
From the tool's definition Tool name 'get_trading_wallets' indicates retrieval of wallet data. Server purpose is to 'analyze wallets' trading activity and profitability', and sibling tools (get_alpha_wallets, get_total_wallets, get_trading_wallet_distribution) are all read-only queries…
Attacks that exploit this kind of access
get_trading_wallets. It is categorised as a Read tool in the Pumpfun Wallets MCP Server, which means it retrieves data without modifying state.
Register the Pumpfun Wallets MCP server in PolicyLayer and add a rule for get_trading_wallets: 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 Pumpfun Wallets. Nothing to install.
get_trading_wallets 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_trading_wallets 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_trading_wallets. 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_trading_wallets is provided by the Pumpfun Wallets MCP server (kukapay/pumpfun-wallets-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 →