Get the currently configured network mode (mainnet_only, testnet_only, both)
AI agents call get_network_mode to retrieve information from Neo N3 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 simple read operation that queries network mode configuration without side effects. No data is modified, no contracts invoked, no assets transferred, and no code executed. While the server provides access to blockchain operations including financial functions (transfer_assets) and destructive ones (deploy_contract), this specific tool only retrieves static configuration information.
From the tool's definition Tool retrieves configuration state ('Get the currently configured network mode') with no modification or execution capability. Returns one of three predefined values (mainnet_only, testnet_only, both).
Attacks that exploit this kind of access
Get the currently configured network mode (mainnet_only, testnet_only, both). It is categorised as a Read tool in the Neo N3 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Neo N3 MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_network_mode 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 get_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 get_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.
get_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 →