Get holders of a specific token by mint address
AI agents call getTokenHolders to retrieve information from AMOCA Solana MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves holder information for a token—a read-only operation that queries blockchain data without modifying state, creating obligations, executing commands, or deleting data. The most severe risk is information disclosure (e.g., identifying whale addresses), which is low severity in the context of public blockchain data that is already transparently queryable on-chain.
From the tool's definition Tool name 'getTokenHolders' and description 'Get holders of a specific token by mint address' indicate a query/retrieval operation with no side effects. This is a data retrieval endpoint that queries blockchain state.
Attacks that exploit this kind of access
Get holders of a specific token by mint address. It is categorised as a Read tool in the AMOCA Solana MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AMOCA Solana MCP Server MCP server in PolicyLayer and add a rule for getTokenHolders: 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 AMOCA Solana MCP Server. Nothing to install.
getTokenHolders 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 getTokenHolders 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 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.
getTokenHolders is provided by the AMOCA Solana MCP Server MCP server (manolaz/amoca-solana-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →