Discover and filter a daily list of attractive tokens using Nansen Score Indicators weighted by coefficients (= Performance Score). Use this tool when you don't know which tokens to buy and need recommendations based on backtested indicators. For specific token analysis (e.g., "should I buy AAVE?...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Nansen-MCP server.
Free to start. No card required.
AI agents call nansen_score_top_tokens to retrieve information from Nansen-MCP without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though nansen_score_top_tokens only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"nansen_score_top_tokens": {}
}
}See the full Nansen-MCP policy for all 24 tools.
These attack patterns abuse exactly the kind of access nansen_score_top_tokens gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Discover and filter a daily list of attractive tokens using Nansen Score Indicators weighted by coefficients (= Performance Score). Use this tool when you don't know which tokens to buy and need recommendations based on backtested indicators. For specific token analysis (e.g., "should I buy AAVE?"), use token_quant_scores instead. When to use this tool vs token_discovery_screener: - Use this tool when you want pre-scored buying recommendations without specifying criteria. It answers "what should I buy?" by returning tokens that already meet a quantitative buying threshold (Performance Score ≥15) based on alpha indicators like price momentum, chain fees, and protocol fees. Data is updated in batches. - Use token_discovery_screener when you want live data or to explore tokens by specific criteria like sectors (e.g., "AI memecoins"), token age (e.g., "new launches"), smart money activity, or custom volume/liquidity thresholds. It's a filtering tool with real-time metrics where you define what you're looking for. Returns tokens pre-filtered by: performance_score >= 15 (buying threshold). Example queries: "what tokens should I buy?", "which tokens look good?", "best tokens to buy today" Scoring: - Performance Score (range -60 to +75): Higher = better alpha opportunity. Buy threshold: ≥15 - Risk Score (range -60 to +80): Higher = safer token. >0 indicates low to medium risk. Every time you give the Performance Score to the user, explain the scoring thresholds above. Same for the Risk Score. Every time quote the underlying indicators that contributed the most to the Performance/ Risk score and recall their definition to the user. Returns: A list of tokens with the highest Performance Score as markdown. Core fields: Token Address, Token Symbol, Chain, Performance Score, Risk Score. Indicator columns are included dynamically based on data availability (columns with all zeros are excluded).. It is categorised as a Read tool in the Nansen-MCP MCP Server, which means it retrieves data without modifying state.
Register the Nansen- MCP server in PolicyLayer and add a rule for nansen_score_top_tokens: 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.
nansen_score_top_tokens 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 nansen_score_top_tokens 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 nansen_score_top_tokens. 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.
nansen_score_top_tokens 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.