Switch between mainnet, testnet, and devnet
AI agents use iota_wallet_switch_network to create or update resources in Iota Agent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Iota Agent environment.
This tool changes the active network configuration for the IOTA wallet/agent. It modifies the operational context (which blockchain network is active), which is a reversible Write-category action. However, misuse could be severe: switching to mainnet when the agent believes it's on testnet could result in real financial transactions being executed on subsequent operations.
From the tool's definition Switch between mainnet, testnet, and devnet
Documented attack patterns abuse exactly the kind of access iota_wallet_switch_network gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Iota Agent, and nothing reaches the server without passing your rules. This is the rule we recommend for iota_wallet_switch_network:
{
"version": "1",
"default": "deny",
"tools": {
"iota_wallet_switch_network": {
"limits": [
{
"counter": "iota_wallet_switch_network_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}iota_wallet_switch_network 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.
Free to start. No card required.
Switch between mainnet, testnet, and devnet. It is categorised as a Write tool in the Iota Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Iota Agent MCP server in PolicyLayer and add a rule for iota_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 Iota Agent. Nothing to install.
iota_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 iota_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 iota_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.
iota_wallet_switch_network is provided by the Iota Agent MCP server (scottcjn/iota-agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 Iota Agent tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
18 Iota Agent tools catalogued and risk-classified — across an index of 42,500+ MCP servers.