Check whether an IP address is detected as a VPN, proxy, other anonymizing service; is on an abuse blocklist; or is a hosting provider. Can look up any IPv4 or IPv6 address, or your own IP if no address is provided.
AI agents call lookup_ip_address_privacy to retrieve information from IPLocate without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure query/lookup operation that retrieves publicly available geolocation and network metadata. It has no side effects, cannot modify data, execute commands, or cause financial transactions. The low severity reflects that misuse would only expose non-sensitive routing/network information that is typically public.
From the tool's definition Tool performs lookups and checks on IP addresses ('Check whether an IP address is detected', 'Can look up any IPv4 or IPv6 address') with no modification, deletion, or execution of code.
Documented attack patterns abuse exactly the kind of access lookup_ip_address_privacy gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and IPLocate, and nothing reaches the server without passing your rules. This is the rule we recommend for lookup_ip_address_privacy:
{
"version": "1",
"default": "deny",
"tools": {
"lookup_ip_address_privacy": {}
}
}lookup_ip_address_privacy is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check whether an IP address is detected as a VPN, proxy, other anonymizing service; is on an abuse blocklist; or is a hosting provider. Can look up any IPv4 or IPv6 address, or your own IP if no address is provided. It is categorised as a Read tool in the IPLocate MCP Server, which means it retrieves data without modifying state.
Register the IPLocate MCP server in PolicyLayer and add a rule for lookup_ip_address_privacy: 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 IPLocate. Nothing to install.
lookup_ip_address_privacy 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 lookup_ip_address_privacy 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 lookup_ip_address_privacy. 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.
lookup_ip_address_privacy is provided by the IPLocate MCP server (iplocate/mcp-server-iplocate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from IPLocate, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 IPLocate tools catalogued and risk-classified — across an index of 43,000+ MCP servers.