calculate_distance
AI agents call calculate_distance to retrieve information from GeoIP 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 creating some uncertainty, the tool's position within a geolocation service and its name imply a computational query on geographic data. No write, delete, execute, or financial operations are evident. The tool would retrieve or compute information based on coordinates already obtained from geolocate_ip or similar tools, making it a Read operation with low severity.
From the tool's definition Tool name 'calculate_distance' on a GeoIP server suggests querying or computing distances between coordinates. The server provides geolocation data (country, city, coordinates, ASN).
Attacks that exploit this kind of access
calculate_distance. It is categorised as a Read tool in the GeoIP MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GeoIP MCP Server MCP server in PolicyLayer and add a rule for calculate_distance: 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 GeoIP MCP Server. Nothing to install.
calculate_distance 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 calculate_distance 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 calculate_distance. 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.
calculate_distance is provided by the GeoIP MCP Server MCP server (mamorett/mcp_geoip2). 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 →