Get upto 25 (per page) top holders information for a specific token. Note: Using labelType: smart_money is not a good proxy for an overall market view. Use it only if user explicitly requests it, or to combine it with other non smart money data. Modes: - onchain_tokens (default): Analyze on-chain...
Part of the Nansen-MCP server.
Free to start. No card required.
AI agents use token_current_top_holders to create or modify resources in Nansen-MCP. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call token_current_top_holders repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Nansen-MCP.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"token_current_top_holders": {
"limits": [
{
"counter": "token_current_top_holders_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Nansen-MCP policy for all 24 tools.
These attack patterns abuse exactly the kind of access token_current_top_holders gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Get upto 25 (per page) top holders information for a specific token. Note: Using labelType: smart_money is not a good proxy for an overall market view. Use it only if user explicitly requests it, or to combine it with other non smart money data. Modes: - onchain_tokens (default): Analyze on-chain tokens by contract address - perps: Analyze Hyperliquid perpetual futures by symbol (chain auto-set to "hyperliquid") Columns returned (onchain_tokens mode): - Address: Wallet/contract address of the token holder - Label: Nansen label (e.g., exchange, whale, etc.) - Balance: Current balance held (numeric with K/M/B formatting) - Balance USD: USD value of token holdings (currency formatted) - Ownership %: Percentage of total token supply owned (percentage, 2 decimal places) - Sent: Total tokens sent from this address historically (numeric) - Received: Total tokens received by this address historically (numeric) - 24h Change: Balance change in last 24 hours (numeric, can be negative) - 7d Change: Balance change in last 7 days (numeric, can be negative) - 30d Change: Balance change in last 30 days (numeric, can be negative) Columns returned (perps mode): - Trader Address: Address of the trader - Trader Label: Nansen label for the trader - Side: Position direction (Long/Short) - Position Value USD: Total USD value of the position (currency formatted) - Position Size: Size of the position in tokens (numeric) - Leverage: Leverage multiplier (e.g., "20X") - Leverage Type: Type of leverage (cross/isolated) - Entry Price: Average entry price (price formatted) - Mark Price: Current mark price (price formatted) - Liquidation Price: Liquidation price (price formatted) - Funding USD: Cumulative funding payments (currency formatted) - Unrealized PnL USD: Unrealized profit/loss (currency formatted) Sorting Options (default: amount desc): onchain_tokens mode: amount, valueUsd, total_outflow, total_inflow, balance_change_24h, balance_change_7d, balance_change_30d, ownership_percentage perps mode: position_size, position_value_usd, entry_price, leverage, upnl_usd, funding_usd, mark_price, liquidation_price Examples: # On-chain tokens (default mode) { "mode": "onchain_tokens", "chain": "ethereum", "token_address": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "label_type": "top_100_holders" } # Hyperliquid perpetual futures { "mode": "perps", "token_address": "PENGU", "label_type": "smart_money" } # Find most active senders using filters { "mode": "onchain_tokens", "chain": "ethereum", "token_address": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "label_type": "smart_money", "includeSmartMoneyLabels": ["All Time Smart Trader", "Fund"], "order_by": "total_outflow", "order_by_direction": "desc" } # Find biggest accumulators (who received most tokens) { "mode": "onchain_tokens", "chain": "ethereum", "token_address": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "label_type": "whale", "order_by": "total_inflow", "order_by_direction": "desc" } # Perps mode with filters { "mode": "perps", "token_address": "ETH", "label_type": "smart_money", "side": "Long", "upnlUsd": {"from": 10000}, "positionValueUsd": {"from": 100000}, "order_by": "position_value_usd", "order_by_direction": "desc" } Restrictions exclusively when querying for native tokens (ETH, BNB, etc.): - Only supports sorting by order_by='balance' (others will fail) - With label_type='top_100_holders': limited filters (balance, total_outflow, total_inflow, address, smart money labels) - For advanced filters, use differentlabel_type or set aggregate_by_entity=true orderBy Restrictions (use 'balance' to avoid API errors): - Token address: 0xa0b86a33e6b6c4b3add000b44b3a1234567890ab Does not work for the following native tokens, DO NOT call with these as you will get an error: - tokenAddress So11111111111111111111111111111111111111112 (SOL on solana chain).. It is categorised as a Write tool in the Nansen-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nansen- MCP server in PolicyLayer and add a rule for token_current_top_holders: 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 Nansen-MCP. Nothing to install.
token_current_top_holders is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the token_current_top_holders 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 token_current_top_holders. 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.
token_current_top_holders is provided by the Nansen- MCP server (nansen-ai/Nansen-MCP). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 24 Nansen-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.