geo_distance
Geodesic distance and bearings on the WGS-84 ellipsoid: Vincenty (millimetre accuracy) plus great-circle haversine, initial / final bearing with 16-point compass, midpoint, multi-point path length with per-segment legs, and the destination point from a start, bearing and distance. Units km, m, mi...
This record as markdown: /tools/com-it-scorptech-x402/geo-distance.md
What geo_distance does on ScorpTech x402 API
AI agents invoke geo_distance to trigger actions in ScorpTech x402 API. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | — | End "lat,lon" |
from | string | — | Start "lat,lon" (decimal degrees) |
units | string | — | |
points | array | — | Path: list of "lat,lon" (total length + legs) |
bearing | number | — | With from + distance: destination mode |
distance | number | — | Distance to travel in the chosen units (destination mode) |
Parameters from the server's own tool schema.
Why geo_distance is rated High
geo_distance triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs geo_distance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For geo_distance, this is the rule to start with:
geo_distance stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every geo_distance call is checked against it from then on.
Questions about geo_distance
Geodesic distance and bearings on the WGS-84 ellipsoid: Vincenty (millimetre accuracy) plus great-circle haversine, initial / final bearing with 16-point compass, midpoint, multi-point path length with per-segment legs, and the destination point from a start, bearing and distance. Units km, m, mi, nautical miles or feet. Offline, deterministic. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/geo-distance. It is categorised as a Execute tool in the ScorpTech x402 API MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
geo_distance accepts 6 parameters: to, from, units, points, bearing, distance. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for geo_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 ScorpTech x402 API. Nothing to install.
geo_distance is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the geo_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 geo_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.
geo_distance is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
Across the catalogue