切换当前使用的钱包
AI agents use switch_wallet to create or update resources in Blockchain Payment MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Blockchain Payment MCP Server environment.
This is a Write operation because it modifies the system's state by changing which wallet is in use, but the change is fully reversible. Although the server handles financial operations (send_transaction, payments), the switch_wallet tool itself does not move money or create financial obligations—it merely changes context.
From the tool's definition Tool name 'switch_wallet' and description indicate it changes the currently active wallet selection. This modifies application state (which wallet is 'current') reversibly—the prior wallet selection can be restored by switching back.
Attacks that exploit this kind of access
切换当前使用的钱包. It is categorised as a Write tool in the Blockchain Payment MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Blockchain Payment MCP Server MCP server in PolicyLayer and add a rule for switch_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.
switch_wallet is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the switch_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 switch_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.
switch_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 →