列出所有已添加的钱包
AI agents call list_wallets to retrieve information from Blockchain Payment MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays wallet information already stored in the system. It has no side effects, does not execute transactions, does not create or modify wallets, and does not move funds. It is a pure read operation that queries wallet state, consistent with the 'list' and 'get' patterns for the Read category. Even though the server handles financial operations, this specific tool only reads wallet metadata.
From the tool's definition Tool name 'list_wallets' and description '列出所有已添加的钱包' (list all added wallets) indicate a retrieval operation that queries wallet data without modification or execution of transactions.
Attacks that exploit this kind of access
列出所有已添加的钱包. It is categorised as a Read tool in the Blockchain Payment MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Blockchain Payment MCP Server MCP server in PolicyLayer and add a rule for list_wallets: 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 Blockchain Payment MCP Server. Nothing to install.
list_wallets 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 list_wallets 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 list_wallets. 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.
list_wallets is provided by the Blockchain Payment MCP Server MCP server (logos-42/blockchain-payment-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 →