AI agents call get_child_account 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 retrieves blockchain data (child account information) without creating, modifying, deleting, executing code, or moving funds. It is a simple read operation querying the Flow blockchain state. The blast radius is minimal—misuse would only expose read access to publicly queryable blockchain data, with no capability to alter state or trigger external operations.
From the tool's definition Tool name 'get_child_account' and description 'Get child accounts for a Flow address' indicate a query/retrieval operation with no side effects. The description explicitly states it retrieves information about child accounts associated with a Flow address.
Attacks that exploit this kind of access
Get child accounts 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_child_account: 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_child_account 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_child_account 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_child_account. 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_child_account 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 →