AI agents call distance_between_addresses to retrieve information from MCP-Geo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query/calculation operation that retrieves distance information based on input addresses. It has no side effects—it reads or computes data without modifying, deleting, or executing external operations. The calculation of distance between addresses is a pure Read operation. Despite the empty description, the function name and server purpose make the classification highly likely.
From the tool's definition Tool name 'distance_between_addresses' combined with server context (GeoPy geocoding) indicates this tool retrieves/calculates distance data between geographic locations. The description is empty, which slightly lowers confidence.
Documented attack patterns abuse exactly the kind of access distance_between_addresses gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Geo, and nothing reaches the server without passing your rules. This is the rule we recommend for distance_between_addresses:
{
"version": "1",
"default": "deny",
"tools": {
"distance_between_addresses": {}
}
}distance_between_addresses 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.
distance_between_addresses. It is categorised as a Read tool in the MCP-Geo MCP Server, which means it retrieves data without modifying state.
Register the MCP-Geo MCP server in PolicyLayer and add a rule for distance_between_addresses: 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 MCP-Geo. Nothing to install.
distance_between_addresses 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 distance_between_addresses 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 distance_between_addresses. 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.
distance_between_addresses is provided by the MCP-Geo MCP server (webcoderz/mcp-geo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 MCP-Geo tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 MCP-Geo tools catalogued and risk-classified — across an index of 42,500+ MCP servers.