Upto 25 results (per page) of trader PnL for a token. Use the sorting and filtering options to narrow down the results. Modes: - onchain_tokens (default): Analyze on-chain tokens by contract address - perps: Analyze Hyperliquid perpetual futures by symbol (chain auto-set to "hyperliquid") NOTE: T...
Part of the Nansen-MCP server.
Free to start. No card required.
AI agents use token_pnl_leaderboard 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_pnl_leaderboard 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_pnl_leaderboard": {
"limits": [
{
"counter": "token_pnl_leaderboard_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_pnl_leaderboard 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.
Upto 25 results (per page) of trader PnL for a token. Use the sorting and filtering options to narrow down the results. Modes: - onchain_tokens (default): Analyze on-chain tokens by contract address - perps: Analyze Hyperliquid perpetual futures by symbol (chain auto-set to "hyperliquid") NOTE: This tool does not support native tokens (so11111111111111111111111111111111111111112, 0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee) in onchain_tokens mode. Returns: Trader performance rankings as markdown. Returns empty string if no trading data found. Columns returned: - Address: Trader's wallet address - Label: Nansen label of the trader - Total PnL: Combined realized and unrealized PnL (currency formatted, can be negative) - Total ROI: Total return on investment as percentage (percentage formatted) - Realized PnL: Profit/loss from completed trades (currency formatted, can be negative) - Realized ROI: Return on investment from realized trades only (percentage formatted) - Unrealized PnL: Current profit/loss on open positions (currency formatted, can be negative) - Unrealized ROI: Return on investment from unrealized positions only (percentage formatted) - Token Holdings: Current token quantity held (numeric formatted) - Holdings USD: Current USD value of token holdings (currency formatted) - Token Price: Current price per token (price formatted) - Peak Token Holdings: Maximum token quantity ever held in the date range (numeric formatted) - Peak Holdings USD: Maximum USD value ever held in the date range (currency formatted) - Still Holding %: Percentage of peak holdings still held (percentage formatted) - Total Trades: Number of trades executed by this address - Net Flow: Net money flow - negative means net seller (currency formatted, can be negative) Sorting Options You can ONLY sort by pnlUsdTotal, roiPercentTotal, pnlUsdRealised, roiPercentRealised, pnlUsdUnrealised, roiPercentUnrealised, valueUsd, nofTrades, stillHoldingBalanceRatio, netflowAmountUsd Filtering Options: 📋 List filters: traderAddress, fullName 📊 Numeric range filters: All sorting fields PLUS holdingAmount, nofBuys, nofSells, boughtAmount, soldAmount, boughtUsd, soldUsd, maxBalanceHeld, maxBalanceHeldUsd Examples: # On-chain tokens (default mode) { "mode": "onchain_tokens", "chain": "ethereum", "tokenAddress": "0xa0b86a33e6ba3e5b9e4b1b1b1b1b1b1b1b1b1b1b", "dateRange": {"from": "30D_AGO", "to": "NOW"}, "order_by": "pnlUsdTotal", "order_by_direction": "desc" } # Hyperliquid perpetual futures { "mode": "perps", "tokenAddress": "ETH", "dateRange": {"from": "7D_AGO", "to": "NOW"} } # Advanced filtering: Find profitable active traders with significant holdings { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6ba3e5b9e4b1b1b1b1b1b1b1b1b1b1b", "dateRange": {"from": "30D_AGO", "to": "NOW"}, "pnlUsdTotal": {"from": 1000, "to": 999999999}, "nofTrades": {"from": 5, "to": 100}, "holdingUsd": {"from": 10000, "to": 999999999}, "stillHoldingBalanceRatio": {"from": 0.1, "to": 1.0}, "order_by": "roiPercentTotal", "order_by_direction": "desc" } Notes: - Ranked by total PnL performance by default - Useful for identifying successful traders and copying strategies - Both ascending and descending sorts provide valuable insights (winners vs losers) - ONLY RETURNS TOP 25 RESULTS for the sort order. Hence the result is NEVER complete. - Make sure the sort order is relevant to your analysis as otherwise you will miss data. This tool does not support hyperevm as 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_pnl_leaderboard: 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_pnl_leaderboard 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_pnl_leaderboard 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_pnl_leaderboard. 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_pnl_leaderboard 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.