network_switch · HashPilot MCP: Risk & Policy

WHAT IT DOES

What network_switch does on HashPilot

AI agents invoke network_switch to trigger actions in HashPilot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why network_switch needs a policy

This tool triggers an external operational change — switching the active network context for all SDK connections, Mirror Node URLs, and RPC endpoints. This is not a simple read or write of data; it executes a reconfiguration of the runtime environment.

From the tool's definition 'Switch between Hedera networks seamlessly' and 'Updates: All SDK connections, Mirror Node URLs, RPC endpoints automatically'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

network_switch Rate-limited

network_switch stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "network_switch": {
      "limits": [
        {
          "counter": "network_switch_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches HashPilot, so you can run agents against it safely.

FAQ

Questions about network_switch

What does the network_switch tool do? +

Switch between Hedera networks seamlessly. NETWORKS: mainnet (production), testnet (testing), previewnet (preview), local (development) UPDATES: All SDK connections, Mirror Node URLs, RPC endpoints automatically USE FOR: Multi-network development, testing across environments, production deployment. It is categorised as a Execute tool in the HashPilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on network_switch? +

Register the HashPilot MCP server in PolicyLayer and add a rule for network_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 HashPilot. Nothing to install.

What risk level is network_switch? +

network_switch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit network_switch? +

Yes. Add a rate_limit block to the network_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.

How do I block network_switch completely? +

Set action: deny in the PolicyLayer policy for network_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.

What MCP server provides network_switch? +

network_switch is provided by the HashPilot MCP server (justmert/hashpilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.