get_coa_account

Get the COA account information for a Flow address on flow blockchain, the flow address is 16 characters long or 18 characters long with 0x prefix NOTE: This is a flow blockchin tool, not for flow EVM chain.

Server Flow MCP outblock/flow-mcp-monorepo
Category Read
Risk class Low
Parameters 00 required

What get_coa_account does on Flow MCP

AI agents call get_coa_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.

Why get_coa_account needs a policy

This tool queries and returns blockchain account information (COA = Cadence Owned Account details) for a given Flow address. It has no side effects, does not modify state, and does not execute code or commands. It is a pure data retrieval operation, fitting the 'Read' category with low severity due to limited blast radius if misused (an agent could only retrieve account details, not modify or spend assets).

From the tool's definition Tool name 'get_coa_account' with description stating 'Get the COA account information' — retrieves data about Cadence Owned Accounts without modifying, deleting, or executing operations.

Questions about get_coa_account

What does the get_coa_account tool do? +

Get the COA account information for a Flow address on flow blockchain, the flow address is 16 characters long or 18 characters long with 0x prefix NOTE: This is a flow blockchin tool, not for flow EVM chain. It is categorised as a Read tool in the Flow MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_coa_account? +

Register the Flow MCP server in PolicyLayer and add a rule for get_coa_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.

What risk level is get_coa_account? +

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

Can I rate-limit get_coa_account? +

Yes. Add a rate_limit block to the get_coa_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.

How do I block get_coa_account completely? +

Set action: deny in the PolicyLayer policy for get_coa_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.

What MCP server provides get_coa_account? +

get_coa_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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.