Used to look up account info by public key (32 byte base58 encoded address)
AI agents call getAccountInfo 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 account information from the Solana blockchain using a public key as input. It performs a query operation without any side effects, data modification, or execution of commands. The public key input is not sensitive (public keys are by definition public on a blockchain). This is a standard read-only RPC method typical of blockchain explorers and wallet interfaces.
From the tool's definition Tool name 'getAccountInfo' and description 'Used to look up account info by public key' indicate a data retrieval operation with no modification capability.
Attacks that exploit this kind of access
Used to look up account info by public key (32 byte base58 encoded 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 getAccountInfo: 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.
getAccountInfo 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 getAccountInfo 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 getAccountInfo. 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.
getAccountInfo 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 →