AI agents call get_directions to retrieve information from Google Maps Platform MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get_directions retrieves route or navigation information from Google Maps. This is a query operation that returns data without creating, modifying, deleting, or executing external actions. The lack of a description slightly reduces confidence, but the pattern of sibling tools and server scope strongly indicate read-only behavior typical of mapping APIs.
From the tool's definition Tool name is 'get_directions' and sibling tools on the server are all read-only queries (find_place, get_distance, get_geocode, place_details, place_nearby).
Documented attack patterns abuse exactly the kind of access get_directions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Maps Platform MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_directions:
{
"version": "1",
"default": "deny",
"tools": {
"get_directions": {}
}
} get_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_directions. It is categorised as a Read tool in the Google Maps Platform MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Maps Platform MCP Server MCP server in PolicyLayer and add a rule for get_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 Google Maps Platform MCP Server. Nothing to install.
get_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_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_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_directions is provided by the Google Maps Platform MCP Server MCP server (neutrollized/google-maps-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Maps Platform 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 Google Maps Platform MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.