Calculate geodetic distance between points.
AI agents call calculate_geodetic_distance to retrieve information from GIS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a mathematical computation on geospatial data that returns a measurement result. It has no side effects on data or systems—it only processes input coordinates and returns a distance value. This is a classic Read operation: retrieves/computes data without modification or external effects.
From the tool's definition Tool name 'calculate_geodetic_distance' and description 'Calculate geodetic distance between points' indicate a pure calculation/query operation. No creation, modification, deletion, execution of arbitrary code, or financial operations occur.
Documented attack patterns abuse exactly the kind of access calculate_geodetic_distance gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GIS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for calculate_geodetic_distance:
{
"version": "1",
"default": "deny",
"tools": {
"calculate_geodetic_distance": {}
}
} calculate_geodetic_distance is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Calculate geodetic distance between points. It is categorised as a Read tool in the GIS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GIS MCP Server MCP server in PolicyLayer and add a rule for calculate_geodetic_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 GIS MCP Server. Nothing to install.
calculate_geodetic_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_geodetic_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_geodetic_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_geodetic_distance is provided by the GIS MCP Server MCP server (mahdin75/gis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GIS MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
98 GIS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.