Compute geodesic great-circle distance in nautical miles (ignores route, this is shortest distance on a sphere).
AI agents call compute_geodesic to retrieve information from Searoute without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a read-only calculation of distance between geographic points. It has no side effects, does not execute code or shell commands, does not create or modify data, and does not delete or move resources. It is a simple distance computation utility suitable for maritime planning context. The blast radius of misuse is minimal—an agent could only be given incorrect distance information.
From the tool's definition Tool description indicates it 'Compute[s] geodesic great-circle distance in nautical miles' with explicit note that it 'ignores route, this is shortest distance on a sphere'.
Documented attack patterns abuse exactly the kind of access compute_geodesic gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Searoute, and nothing reaches the server without passing your rules. This is the rule we recommend for compute_geodesic:
{
"version": "1",
"default": "deny",
"tools": {
"compute_geodesic": {}
}
}compute_geodesic 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.
Compute geodesic great-circle distance in nautical miles (ignores route, this is shortest distance on a sphere). It is categorised as a Read tool in the Searoute MCP Server, which means it retrieves data without modifying state.
Register the Searoute MCP server in PolicyLayer and add a rule for compute_geodesic: 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 Searoute. Nothing to install.
compute_geodesic 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 compute_geodesic 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 compute_geodesic. 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.
compute_geodesic is provided by the Searoute MCP server (project-harrison/searoute-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Searoute, 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.
3 Searoute tools catalogued and risk-classified — across an index of 43,000+ MCP servers.