Set the network mode (mainnet_only, testnet_only, both). Requires restart.
AI agents use set_network_mode to create or update resources in Neo N3 MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Neo N3 MCP Server environment.
The tool changes application configuration (network mode selection) which affects the runtime behavior of the MCP server and its subsequent blockchain interactions. This is a reversible configuration change rather than destructive deletion or financial impact. However, it has meaningful side effects (requires restart, redirects all blockchain operations to different networks) making it Write rather than Read.
From the tool's definition Tool description states it 'Set the network mode' with options (mainnet_only, testnet_only, both) and requires restart. This modifies configuration state.
Attacks that exploit this kind of access
Set the network mode (mainnet_only, testnet_only, both). Requires restart. It is categorised as a Write tool in the Neo N3 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Neo N3 MCP Server MCP server in PolicyLayer and add a rule for set_network_mode: 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 Neo N3 MCP Server. Nothing to install.
set_network_mode 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 set_network_mode 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 set_network_mode. 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.
set_network_mode is provided by the Neo N3 MCP Server MCP server (r3e-network/neo-n3-mcp). 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 →