wallet_switch
Switch to a different wallet. Note: The new wallet will need to be unlocked before use.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/wallet-switch.md
What wallet_switch does on Aibtc
AI agents use wallet_switch to create or update resources in Aibtc, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aibtc environment.
Why wallet_switch is rated Medium
Switching the active wallet modifies application state by changing which wallet is currently in use. This is a reversible configuration change (Write), not a financial transaction itself. However, misuse could facilitate unauthorized access to other wallets, hence medium severity. Confidence is moderate as the description is brief and doesn't detail all side effects.
From the tool's definition Switch to a different wallet. The new wallet will need to be unlocked before use.
Attacks that exploit this kind of access
The rule that runs wallet_switch 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_switch, this is the rule to start with:
wallet_switch stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_switch call is checked against it from then on.
Questions about wallet_switch
Switch to a different wallet. Note: The new wallet will need to be unlocked before use. It is categorised as a Write tool in the Aibtc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aibtc MCP server in PolicyLayer and add a rule for wallet_switch: 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_switch 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 wallet_switch 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_switch. 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_switch 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