Get high-level routing information between two or more locations. Includes travel time, distance, and an encoded polyline of the route. The result is JSON.
AI agents call route-overview to retrieve information from Stadia Maps Location API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries routing data from the Stadia Maps API without creating, modifying, deleting, or executing any side-effect operations. It returns read-only information (travel time, distance, route geometry) based on input coordinates. No data is written, resources are not executed, and no irreversible changes occur. This is a straightforward data retrieval operation.
From the tool's definition Tool description states it 'Get[s] high-level routing information' and 'Includes travel time, distance, and an encoded polyline' - purely retrieval of pre-computed routing data with no modification, deletion, or execution of external commands.
Documented attack patterns abuse exactly the kind of access route-overview gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Stadia Maps Location API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for route-overview:
{
"version": "1",
"default": "deny",
"tools": {
"route-overview": {}
}
}route-overview 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.
Get high-level routing information between two or more locations. Includes travel time, distance, and an encoded polyline of the route. The result is JSON. It is categorised as a Read tool in the Stadia Maps Location API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Stadia Maps Location API MCP Server MCP server in PolicyLayer and add a rule for route-overview: 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 Stadia Maps Location API MCP Server. Nothing to install.
route-overview 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 route-overview 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 route-overview. 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.
route-overview is provided by the Stadia Maps Location API MCP Server MCP server (stadiamaps/stadiamaps-mcp-server-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Stadia Maps Location API 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.
6 Stadia Maps Location API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.