Geolocate an IP address (country, region, city, coordinates, time zone) using an offline database, plus its reverse-DNS hostname. No external API. Args: - ip (string): IPv4 or IPv6 address. - response_format (
AI agents call ip_geolocation to retrieve information from Domain Security without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
ip_geolocation queries and returns geographic and DNS metadata about an IP address. It performs lookups against a local database without modifying, executing code, or deleting data. This is a pure Read operation. Severity is low because geolocation data is typically public or semi-public information; misuse would enable reconnaissance but not direct harm.
From the tool's definition Tool 'geolocates' an IP address to retrieve 'country, region, city, coordinates, time zone' and 'reverse-DNS hostname' using an 'offline database' with 'no external API'. These are all information-retrieval operations with no side effects.
Attacks that exploit this kind of access
Geolocate an IP address (country, region, city, coordinates, time zone) using an offline database, plus its reverse-DNS hostname. No external API. Args: - ip (string): IPv4 or IPv6 address. - response_format (. It is categorised as a Read tool in the Domain Security MCP Server, which means it retrieves data without modifying state.
Register the Domain Security MCP server in PolicyLayer and add a rule for ip_geolocation: 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 Domain Security. Nothing to install.
ip_geolocation 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_geolocation 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_geolocation. 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_geolocation is provided by the Domain Security MCP server (ortamarco/domain-security-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ip_geolocation is one line of Domain Security's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →