Low Risk

getAccountInfo

Get detailed account information for a Solana address

How to control getAccountInfo ↓

AI agents call getAccountInfo to retrieve information from Web3 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves blockchain account data without side effects. It queries existing information about a Solana address and returns details, which is characteristic of Read operations. The severity is low because reading public blockchain data poses minimal risk to the system or user assets.

From the tool's definition Tool name 'getAccountInfo' and description 'Get detailed account information for a Solana address' indicate a retrieval operation. The verb 'get' and lack of any modification, execution, or financial language confirm this is a read-only query.

Documented attack patterns abuse exactly the kind of access getAccountInfo gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Web3 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for getAccountInfo:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "getAccountInfo": {}
  }
}

getAccountInfo is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Web3 MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the getAccountInfo tool do? +

Get detailed account information for a Solana address. It is categorised as a Read tool in the Web3 MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getAccountInfo? +

Register the Web3 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 Web3 MCP Server. Nothing to install.

What risk level is getAccountInfo? +

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

Can I rate-limit getAccountInfo? +

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.

How do I block getAccountInfo completely? +

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.

What MCP server provides getAccountInfo? +

getAccountInfo is provided by the Web3 MCP Server MCP server (strangelove-ventures/web3-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Web3 MCP Server tool call.

Deterministic rules across all 55 Web3 MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

55 Web3 MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.