AI agents call get_route_directions to retrieve information from OpenStreetMap MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries routing/direction data and returns it without modifying any underlying data or triggering external actions. It fits the Read pattern: retrieve or query data with no side effects. Confidence is moderate (0.75) rather than high because the description is empty, but the name and server context strongly suggest a data-retrieval operation rather than execution or modification.
From the tool's definition Tool name 'get_route_directions' and server context (geocode, find_nearby_places, analyze_neighborhood, explore_area) indicate this retrieves directional/routing data from OpenStreetMap.
Documented attack patterns abuse exactly the kind of access get_route_directions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenStreetMap MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_route_directions:
{
"version": "1",
"default": "deny",
"tools": {
"get_route_directions": {}
}
}get_route_directions 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_route_directions. It is categorised as a Read tool in the OpenStreetMap MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenStreetMap MCP Server MCP server in PolicyLayer and add a rule for get_route_directions: 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 OpenStreetMap MCP Server. Nothing to install.
get_route_directions 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 get_route_directions 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 get_route_directions. 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.
get_route_directions is provided by the OpenStreetMap MCP Server MCP server (jagan-shanmugam/open-streetmap-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OpenStreetMap 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.
12 OpenStreetMap MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.