get_token_holders

Get the top holders of a SIP-010 token.

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/get-token-holders.md

WHAT IT DOES

What get_token_holders does on Aibtc

AI agents call get_token_holders to retrieve information from Aibtc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_token_holders is rated Low

This tool queries and retrieves information about token holders on the blockchain. It has no side effects—it does not create, modify, delete, or execute operations. The action is a simple data retrieval (get) from public blockchain state. Even though the server context includes financial tools like 'alex_swap' and 'bitflow_create_order', this specific tool is purely informational and non-destructive.

From the tool's definition Tool name 'get_token_holders' and description 'Get the top holders of a SIP-010 token' indicate a read operation that retrieves public blockchain data without modifying state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_token_holders safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_token_holders, this is the rule to start with:

get_token_holders Allowed

get_token_holders is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_token_holders": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every get_token_holders call is checked against it from then on.

FAQ

Questions about get_token_holders

What does the get_token_holders tool do? +

Get the top holders of a SIP-010 token. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_token_holders? +

Register the Aibtc MCP server in PolicyLayer and add a rule for get_token_holders: 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 Aibtc. Nothing to install.

What risk level is get_token_holders? +

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

Can I rate-limit get_token_holders? +

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

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

get_token_holders is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 358 Aibtc tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →