haversine
Great-Circle Distance (haversine) — Distance (km/mi/nautical) and initial bearing between two lat/lon points.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/haversine.md
What haversine does on Gateway
AI agents call haversine to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
lat1 | number | Yes | Latitude of point 1 (-90..90) |
lat2 | number | Yes | Latitude of point 2 (-90..90) |
lon1 | number | Yes | Longitude of point 1 (-180..180) |
lon2 | number | Yes | Longitude of point 2 (-180..180) |
Parameters from the server's own tool schema.
Why haversine is rated Low
This is a pure calculation tool that retrieves geometric information derived from input parameters. It has no side effects, creates no persistent data, executes no external operations, and poses minimal risk even if misused by an agent—worst case it provides incorrect distance estimates.
From the tool's definition Tool performs distance and bearing calculation from latitude/longitude coordinates with no modification of data ('Distance... between two lat/lon points'). Returns computed values only.
Attacks that exploit this kind of access
The rule that runs haversine safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For haversine, this is the rule to start with:
haversine is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every haversine call is checked against it from then on.
Questions about haversine
Great-Circle Distance (haversine) — Distance (km/mi/nautical) and initial bearing between two lat/lon points. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
haversine accepts 4 parameters: lat1, lat2, lon1, lon2. Required: lat1, lat2, lon1, lon2. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for haversine: 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 Gateway. Nothing to install.
haversine 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 haversine 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 haversine. 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.
haversine is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue