使用 Routes API 获取两点之间的路线指导
AI agents call maps_directions to retrieve information from Google Maps 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 the Google Maps Routes API to fetch directional information between locations. It is purely informational and retrieves data without creating, modifying, deleting, or executing external operations. The capability to get directions is a standard Read operation—similar to search or fetch functions. There is no destructive, financial, or code-execution component.
From the tool's definition The tool 'maps_directions' uses the Routes API to retrieve route guidance between two points. The description indicates it 'gets' or 'obtains' (获取) route information, which is a retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
使用 Routes API 获取两点之间的路线指导. It is categorised as a Read tool in the Google Maps MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Maps MCP Server MCP server in PolicyLayer and add a rule for maps_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 MCP Server. Nothing to install.
maps_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 maps_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 maps_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.
maps_directions is provided by the Google Maps MCP Server MCP server (lesonky/google-maps-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →