High Risk →

token_quant_scores

Get Nansen Score Indicators for a token - quantitative risk and reward signals. Use this tool when assessing a token's risk/reward profile, evaluating buy/sell decisions, or when the user needs quantitative data to make trading decisions. Returns: Token risk/reward indicators as markdown with int...

Risk signalsBulk/mass operation — affects multiple targets

Part of the Nansen-MCP server.

token_quant_scores can trigger actions in Nansen-MCP, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE NANSEN-MCP →

Free to start. No card required.

AI agents invoke token_quant_scores to trigger processes or run actions in Nansen-MCP. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

token_quant_scores can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "token_quant_scores": {
      "limits": [
        {
          "counter": "token_quant_scores_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Nansen-MCP policy for all 24 tools.

Get this rule live on your own Nansen-MCP server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY NANSEN-MCP →

View all 24 tools →

These attack patterns abuse exactly the kind of access token_quant_scores gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so token_quant_scores only ever does what you allow.

SECURE NANSEN-MCP →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the token_quant_scores tool do? +

Get Nansen Score Indicators for a token - quantitative risk and reward signals. Use this tool when assessing a token's risk/reward profile, evaluating buy/sell decisions, or when the user needs quantitative data to make trading decisions. Returns: Token risk/reward indicators as markdown with interpretation guidance. Token info: - Market Cap: Current market cap in USD - Market Cap Group: largecap (>$1B), midcap ($100M-$1B), or lowcap (<$100M) - Is Stablecoin: Whether token is a stablecoin (some indicators don't apply to stablecoins) Fields returned per indicator: - Score: Signal classification (bullish/neutral/bearish for reward; low/medium/high for risk) - Signal: Raw numeric value of the indicator - Percentile: Rank vs same market cap group (0-100%) - Last Trigger: Date when signal was last calculated Indicator types: - Reward Indicators: price-momentum, funding-rate, chain-fees, chain-tvl, protocol-fees, trading-range - Risk Indicators: btc-reflexivity, liquidity-risk, token-supply-inflation, concentration-risk, cex-flows Notes: - Not all indicators available for every token/chain combination - Percentile compares against same market cap group (largecap >$1B, midcap $100M-$1B, lowcap <$100M). It is categorised as a Execute tool in the Nansen-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on token_quant_scores? +

Register the Nansen- MCP server in PolicyLayer and add a rule for token_quant_scores: 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.

What risk level is token_quant_scores? +

token_quant_scores is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit token_quant_scores? +

Yes. Add a rate_limit block to the token_quant_scores 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.

How do I block token_quant_scores completely? +

Set action: deny in the PolicyLayer policy for token_quant_scores. 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.

What MCP server provides token_quant_scores? +

token_quant_scores 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.

Enforce policy on every Nansen-MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.