Switch between mainnet and testnet.
AI agents use wallet_switch_network to create or update resources in Bitcoin wallet MCP server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bitcoin wallet MCP server environment.
Switching networks is a reversible configuration change that affects subsequent wallet operations (sends, receives, balance checks would now operate on a different blockchain). It modifies wallet state but does not permanently destroy data or move funds.
From the tool's definition The tool is described as 'Switch between mainnet and testnet,' which modifies the active network configuration of the wallet. This changes the wallet's state to point to a different blockchain network.
Attacks that exploit this kind of access
Switch between mainnet and testnet. It is categorised as a Write tool in the Bitcoin wallet MCP server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bitcoin wallet MCP server MCP server in PolicyLayer and add a rule for wallet_switch_network: 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 Bitcoin wallet MCP server. Nothing to install.
wallet_switch_network 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_network 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_network. 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_network is provided by the Bitcoin wallet MCP server MCP server (markmhendrickson/mcp-server-bitcoin). 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 →