wallet_list_accounts
List wallet accounts with their nicknames and addresses. By default returns only ACTIVE accounts (signable). Pass { archived: true } to return ARCHIVED accounts instead — these are accounts whose mnemonic could not be recovered from the OS keychain at startup (e.g., wallet.db moved to a new machi...
This record as markdown: /tools/goplausible-algorand-mcp/wallet-list-accounts.md
What wallet_list_accounts does on Algorand MCP
AI agents call wallet_list_accounts to retrieve information from Algorand MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why wallet_list_accounts is rated Low
This tool only queries and returns account metadata (nicknames and addresses) from the wallet database. It performs no side effects, does not execute transactions, does not modify state, and does not create financial obligations. The optional 'archived' parameter only filters which accounts are returned, not the nature of the operation itself. This is a straightforward read/query operation.
From the tool's definition Tool name is 'wallet_list_accounts' and description states it 'List wallet accounts with their nicknames and addresses' — a retrieval operation with no modification, deletion, or execution of transactions.
Attacks that exploit this kind of access
The rule that runs wallet_list_accounts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Algorand MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wallet_list_accounts, this is the rule to start with:
wallet_list_accounts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Algorand MCP, apply this rule, and every wallet_list_accounts call is checked against it from then on.
Questions about wallet_list_accounts
List wallet accounts with their nicknames and addresses. By default returns only ACTIVE accounts (signable). Pass { archived: true } to return ARCHIVED accounts instead — these are accounts whose mnemonic could not be recovered from the OS keychain at startup (e.g., wallet.db moved to a new machine without keychain, or fresh Docker install over an existing DB). Archived rows stay in the DB for forensics but cannot sign; their nicknames are freed for reuse by new active accounts. It is categorised as a Read tool in the Algorand MCP MCP Server, which means it retrieves data without modifying state.
Register the Algorand MCP server in PolicyLayer and add a rule for wallet_list_accounts: 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. Nothing to install.
wallet_list_accounts 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 wallet_list_accounts 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 wallet_list_accounts. 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.
wallet_list_accounts is provided by the Algorand MCP server (goplausible/algorand-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Algorand, and thousands of servers like it.
This server
Across the catalogue