wallet_list
List all wallets available for the agent to use.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/wallet-list.md
What wallet_list does on Aibtc
AI agents call wallet_list to retrieve information from Aibtc 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 is rated Low
This tool queries and returns information about available wallets without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal blast radius—disclosure of wallet identifiers could inform further attacks, but the tool itself performs no mutations or financial transactions.
From the tool's definition Tool name is 'wallet_list' and description states 'List all wallets available for the agent to use.' The verb 'list' indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs wallet_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wallet_list, this is the rule to start with:
wallet_list 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 Aibtc, apply this rule, and every wallet_list call is checked against it from then on.
Questions about wallet_list
List all wallets available for the agent to use. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.
Register the Aibtc MCP server in PolicyLayer and add a rule for wallet_list: 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 Aibtc. Nothing to install.
wallet_list 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 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. 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 is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
This server
Across the catalogue