get_trading_wallet_distribution
AI agents call get_trading_wallet_distribution 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.
The tool appears to fetch or query distribution data from the Pump.fun/PumpSwap ecosystem without modifying data. The empty description lowers confidence slightly, but the consistent pattern of 'get_*' sibling tools and the server's stated purpose of analysis (not modification) strongly indicates this is a Read operation with no side effects.
From the tool's definition Tool name 'get_trading_wallet_distribution' suggests data retrieval about wallet distribution metrics. Server description states it 'analyzes wallets' trading activity and profitability', indicating Read-only query operations.
Attacks that exploit this kind of access
get_trading_wallet_distribution. 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_wallet_distribution: 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_wallet_distribution 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_wallet_distribution 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_wallet_distribution. 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_wallet_distribution 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 →