Get IP ranges owned by a domain/organization.
AI agents call get_ip_ranges to retrieve information from IPInfo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing public IP address range data without modifying, deleting, executing code, or moving funds. It is a straightforward information query operation similar to other Read-category tools on the server (e.g., get_ip_info, get_company_info). The severity is low because misuse would only expose publicly available network information, creating minimal risk to the user or target systems.
From the tool's definition Tool name 'get_ip_ranges' and description 'Get IP ranges owned by a domain/organization' indicate a retrieval operation that queries public IP range information.
Attacks that exploit this kind of access
Get IP ranges owned by a domain/organization. It is categorised as a Read tool in the IPInfo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the IPInfo MCP Server MCP server in PolicyLayer and add a rule for get_ip_ranges: 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 IPInfo MCP Server. Nothing to install.
get_ip_ranges 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_ip_ranges 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_ip_ranges. 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_ip_ranges is provided by the IPInfo MCP Server MCP server (nimblebraininc/mcp-ipinfo). 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 →