移除指定标签的钱包
AI agents call remove_wallet to permanently remove resources in Blockchain Payment MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion operation on wallet data. Even though it is labeled as 'removing' rather than explicitly 'deleting', the semantic meaning is the same: it removes a wallet record by label, which is a destructive action that cannot be reversed.
From the tool's definition Tool name 'remove_wallet' combined with description '移除指定标签的钱包' (Remove wallet with specified label). The action irreversibly deletes wallet records, which cannot be undone and may result in permanent loss of access to funds or wallet data.
Attacks that exploit this kind of access
移除指定标签的钱包. It is categorised as a Destructive tool in the Blockchain Payment MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Blockchain Payment MCP Server MCP server in PolicyLayer and add a rule for remove_wallet: 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.
remove_wallet is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_wallet 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 remove_wallet. 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.
remove_wallet 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 →