subnet
IPv4 Subnet / CIDR Calculator — Network, broadcast, netmask, usable host range and counts for an IPv4 CIDR block.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/subnet.md
What subnet does on Gateway
AI agents call subnet to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
ip | string | — | IPv4 address, e.g. '192.168.1.10' |
cidr | string | — | CIDR string, e.g. '192.168.1.0/24' (or use ip + prefix) |
prefix | integer | — | Prefix length 0-32 |
Parameters from the server's own tool schema.
Why subnet is rated Low
This is a pure calculation/query tool that takes a CIDR block as input and returns computed network information. It has no side effects, does not modify any network configuration, does not execute commands, and does not access or alter data. The blast radius of misuse is minimal—an AI agent could only provide incorrect subnet calculations, which would be caught during actual network operations.
From the tool's definition Tool performs calculation and retrieval of IPv4 subnet properties (network, broadcast, netmask, usable host range and counts) from a given CIDR block. No modification, deletion, or execution of network operations occurs.
Attacks that exploit this kind of access
The rule that runs subnet safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For subnet, this is the rule to start with:
subnet is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every subnet call is checked against it from then on.
Questions about subnet
IPv4 Subnet / CIDR Calculator — Network, broadcast, netmask, usable host range and counts for an IPv4 CIDR block. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
subnet accepts 3 parameters: ip, cidr, prefix. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for 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 Gateway. Nothing to install.
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 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 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.
subnet is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue