Low Risk

smart_traders_and_funds_token_balances

Get aggregated (not per wallet) smart trader and fund (EXCLUDES whales, large holders, influencers, etc.) token balances and 24h change per chain for all chains (default is ['all'], which queries all supported chains) or specific chain(s). Use filters to narrow down the results.

Part of the Nansen-MCP server.

smart_traders_and_funds_token_balances is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE NANSEN-MCP →

Free to start. No card required.

AI agents call smart_traders_and_funds_token_balances 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 smart_traders_and_funds_token_balances 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "smart_traders_and_funds_token_balances": {}
  }
}

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 smart_traders_and_funds_token_balances 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 smart_traders_and_funds_token_balances only ever does what you allow.

SECURE NANSEN-MCP →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the smart_traders_and_funds_token_balances tool do? +

Get aggregated (not per wallet) smart trader and fund (EXCLUDES whales, large holders, influencers, etc.) token balances and 24h change per chain for all chains (default is ['all'], which queries all supported chains) or specific chain(s). Use filters to narrow down the results.. It is categorised as a Read tool in the Nansen-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on smart_traders_and_funds_token_balances? +

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

smart_traders_and_funds_token_balances is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit smart_traders_and_funds_token_balances? +

Yes. Add a rate_limit block to the smart_traders_and_funds_token_balances 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 smart_traders_and_funds_token_balances completely? +

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

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