Calculate the distance between two ZIP codes using either the Haversine or Vincenty formula. Returns origin/destination details and the computed distance.
AI agents call calculate_zip_code_distance to retrieve information from loc8n Geographic Data without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | Yes | Destination ZIP code (5 digits) |
from | string | Yes | Origin ZIP code (5 digits) |
unit | string | — | Distance unit |
method | string | — | Calculation method |
Parameters from the server's own tool schema.
This tool performs a pure computation on geographic coordinates to determine distance. It retrieves and returns calculated data without creating, modifying, deleting, or executing external operations. The operation is deterministic, side-effect-free, and poses minimal risk even if misused by an AI agent—at worst it would return distance calculations. No financial, destructive, or write operations are involved.
From the tool's definition Tool description states it 'Calculate[s] the distance between two ZIP codes' and 'Returns origin/destination details and the computed distance.' The verb 'Calculate' and 'Returns' indicate a read-only query operation with no data modification, deletion, or…
Attacks that exploit this kind of access
Calculate the distance between two ZIP codes using either the Haversine or Vincenty formula. Returns origin/destination details and the computed distance. It is categorised as a Read tool in the loc8n Geographic Data MCP Server, which means it retrieves data without modifying state.
calculate_zip_code_distance accepts 4 parameters: to, from, unit, method. Required: to, from. The full parameter table on this page comes from the server's own tool schema.
Register the loc8n Geographic Data MCP server in PolicyLayer and add a rule for calculate_zip_code_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 loc8n Geographic Data. Nothing to install.
calculate_zip_code_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_zip_code_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_zip_code_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_zip_code_distance is provided by the loc8n Geographic Data MCP server (gener8v/gener8v.mcp.geographic-data). 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 →