Check if an IP is in a subnet and whether it is a usable host address.
AI agents call ip_in_subnet to retrieve information from Network MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a static calculation or lookup to determine IP membership in a subnet range and validates host usability. It has no capability to create, modify, delete, execute code, or move funds. The operation is read-only and informational, with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states it 'Check[s] if an IP is in a subnet and whether it is a usable host address' — a purely query/lookup operation with no side effects. The name 'ip_in_subnet' and description confirm this retrieves information without modifying state.
Attacks that exploit this kind of access
Check if an IP is in a subnet and whether it is a usable host address. It is categorised as a Read tool in the Network MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Network MCP Server MCP server in PolicyLayer and add a rule for ip_in_subnet: 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 Network MCP Server. Nothing to install.
ip_in_subnet 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 ip_in_subnet 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 ip_in_subnet. 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.
ip_in_subnet is provided by the Network MCP Server MCP server (labeveryday/network-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 →