get_plus_ip_info
AI agents call get_plus_ip_info 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.
Despite the empty description, the naming convention (get_plus_ip_info), server context (IP intelligence provider), and consistent pattern of read-only sibling tools all strongly indicate this tool retrieves IP-related data without side effects. Even with the 'plus' suffix (suggesting enhanced or additional data), it remains a data retrieval operation.
From the tool's definition Tool is named 'get_plus_ip_info' and resides on an IPInfo MCP Server described as providing 'IP address intelligence and geolocation lookups' with sibling tools that are all retrieval-based (get_abuse_contact, get_account_info, get_carrier_info,…
Attacks that exploit this kind of access
get_plus_ip_info. 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_plus_ip_info: 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_plus_ip_info 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_plus_ip_info 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_plus_ip_info. 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_plus_ip_info 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 →