ip_in_cidr
IP-in-CIDR Membership Check — Check whether an IPv4 or IPv6 address falls inside a CIDR network block (RFC 4632).
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/ip-in-cidr.md
What ip_in_cidr does on Gateway
AI agents call ip_in_cidr 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 | Yes | IP address (IPv4 or IPv6) |
cidr | string | Yes | CIDR network block, e.g. '10.0.0.0/8' |
Parameters from the server's own tool schema.
Why ip_in_cidr is rated Low
This is a deterministic, read-only lookup function that validates IP addresses against CIDR notation. It retrieves or queries network membership information without creating, modifying, executing code, deleting data, or committing financial transactions.
From the tool's definition Tool performs a membership check query against a CIDR network block without modifying, executing, or deleting anything. The description explicitly states it 'checks whether' an address falls inside a network — a pure query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs ip_in_cidr 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 ip_in_cidr, this is the rule to start with:
ip_in_cidr 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 ip_in_cidr call is checked against it from then on.
Questions about ip_in_cidr
IP-in-CIDR Membership Check — Check whether an IPv4 or IPv6 address falls inside a CIDR network block (RFC 4632). It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
ip_in_cidr accepts 2 parameters: ip, cidr. Required: ip, cidr. 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 ip_in_cidr: 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.
ip_in_cidr 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_cidr 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_cidr. 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_cidr 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