Get all SPL token accounts owned by a wallet address
AI agents call get_token_accounts to retrieve information from 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 queries blockchain data to retrieve information about token accounts associated with a wallet. It performs no modifications, deletions, or financial transactions. The operation is read-only and returns existing data without affecting system state. While used on a financial blockchain (Solana), the tool itself does not move funds or create obligations—it only retrieves account information.
From the tool's definition Tool name 'get_token_accounts' and description 'Get all SPL token accounts owned by a wallet address' indicate a data retrieval operation with no side effects.
Attacks that exploit this kind of access
Get all SPL token accounts owned by a wallet address. It is categorised as a Read tool in the Solana MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Solana MCP Server MCP server in PolicyLayer and add a rule for get_token_accounts: 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 Solana MCP Server. Nothing to install.
get_token_accounts 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 get_token_accounts 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 get_token_accounts. 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.
get_token_accounts is provided by the Solana MCP Server MCP server (visioneth/solana-mcp). 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 →