Get mobile carrier information for an IP address.
AI agents call get_carrier_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.
This tool retrieves carrier metadata for an IP address, which is a non-destructive read operation. It has no side effects, makes no modifications, executes no code, and poses minimal security risk even if misused by an AI agent—at worst, it returns publicly available geolocation/carrier data about IP addresses.
From the tool's definition Tool name 'get_carrier_info' and description 'Get mobile carrier information for an IP address' indicate a query/lookup operation that retrieves data about an IP address without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Get mobile carrier information for an IP address. 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_carrier_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_carrier_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_carrier_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_carrier_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_carrier_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 →