AI agents call get_account_info to retrieve information from Flow MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns account information (balance and storage statistics) from the Flow blockchain. It performs no state changes, executes no code, and has no side effects. The operation is read-only data retrieval, consistent with tools like 'get_flow_balance' on the same server. Blast radius is minimal: misuse would only expose already-public blockchain account data.
From the tool's definition Tool name 'get_account_info' and description states it 'Get detailed account information including balance and storage stats for a Flow address' — purely retrieves data with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get detailed account information including balance and storage stats for a Flow address on flow blockchain, the flow address is 16 characters long or 18 characters long with 0x prefix. It is categorised as a Read tool in the Flow MCP MCP Server, which means it retrieves data without modifying state.
Register the Flow MCP server in PolicyLayer and add a rule for get_account_info: 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 Flow MCP. Nothing to install.
get_account_info 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_account_info 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_account_info. 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_account_info is provided by the Flow MCP server (outblock/flow-mcp-monorepo). 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 →