Low Risk

getTokenHolders

BEST FOR: top holders of a specific token by mint. PREFER getTokenAccounts for advanced token account queries with flexible filters. Get the top 20 holders of a specific SPL token by mint address. Returns holder wallet addresses and their token balances (raw amounts). Useful for checking token di...

Single-target operation

Part of the Helius MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

helius-mcp Read

AI agents call getTokenHolders to retrieve information from Helius 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 getTokenHolders 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.

helius.yaml
tools:
  getTokenHolders:
    rules:
      - action: allow

See the full Helius policy for all 63 tools.

Tool Name getTokenHolders
Category Read
MCP Server Helius MCP Server
Risk Level Low

View all 63 tools →

Agents calling read-class tools like getTokenHolders have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the getTokenHolders tool do? +

BEST FOR: top holders of a specific token by mint. PREFER getTokenAccounts for advanced token account queries with flexible filters. Get the top 20 holders of a specific SPL token by mint address. Returns holder wallet addresses and their token balances (raw amounts). Useful for checking token distribution, finding whale wallets, or verifying token decentralization. Credit cost: ~20 credits/call (10 for token accounts + 10 for token metadata via DAS API).. It is categorised as a Read tool in the Helius MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getTokenHolders? +

Add a rule in your Intercept YAML policy under the tools section for getTokenHolders. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Helius MCP server.

What risk level is getTokenHolders? +

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

Can I rate-limit getTokenHolders? +

Yes. Add a rate_limit block to the getTokenHolders rule in your Intercept 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 getTokenHolders completely? +

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

getTokenHolders is provided by the Helius MCP server (helius-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.