Get all assets held by an account with balances
AI agents call getAccountAssets to retrieve information from Algorand MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a data retrieval operation with no side effects. It queries blockchain data to return a list of assets and their balances for a specified account, similar to other Read-category tools like 'getAccountInfo' and 'getAssetBalance' on the same server. The operation is read-only and poses minimal risk of misuse, warranting a 'low' severity classification.
From the tool's definition Tool name 'getAccountAssets' and description 'Get all assets held by an account with balances' indicate a read-only query operation that retrieves account asset information without modifying any state.
Attacks that exploit this kind of access
Get all assets held by an account with balances. It is categorised as a Read tool in the Algorand MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Algorand MCP Server MCP server in PolicyLayer and add a rule for getAccountAssets: 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 Algorand MCP Server. Nothing to install.
getAccountAssets 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 getAccountAssets 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 getAccountAssets. 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.
getAccountAssets is provided by the Algorand MCP Server MCP server (tairon-ai/algorand-mcp). 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 →