Gets the network the wallet is connected to (mainnet or testnet).
AI agents call wallet_getNetwork to retrieve information from Bitcoin SV MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read operation that queries the current network connection state of a wallet. It has no side effects, makes no modifications, executes no code, and involves no financial transactions. The tool simply returns whether the wallet is on mainnet or testnet—informational metadata only.
From the tool's definition Tool name 'wallet_getNetwork' and description 'Gets the network the wallet is connected to' indicate a query operation that retrieves configuration state without modifying anything.
Documented attack patterns abuse exactly the kind of access wallet_getNetwork gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bitcoin SV MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for wallet_getNetwork:
{
"version": "1",
"default": "deny",
"tools": {
"wallet_getNetwork": {}
}
} wallet_getNetwork is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Gets the network the wallet is connected to (mainnet or testnet). It is categorised as a Read tool in the Bitcoin SV MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bitcoin SV MCP Server MCP server in PolicyLayer and add a rule for wallet_getNetwork: 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 SV MCP Server. Nothing to install.
wallet_getNetwork 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 wallet_getNetwork 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_getNetwork. 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_getNetwork is provided by the Bitcoin SV MCP Server MCP server (b-open-io/bsv-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bitcoin SV MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
80 Bitcoin SV MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.