AI agents call google_maps_directions to retrieve information from Noapi Google Search without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the tool name strongly suggests it retrieves direction data, which is a read operation with no capacity to modify, delete, or execute code. The sibling tools (archive_webpage, get_feed_items, google_books, google_finance, google_flights) are all retrieval-focused.
From the tool's definition Tool name 'google_maps_directions' indicates retrieval of navigation/direction data from Google Maps. The server is designed for querying and fetching information (search, feeds, transcriptions, OCR) without side effects.
Documented attack patterns abuse exactly the kind of access google_maps_directions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Noapi Google Search, and nothing reaches the server without passing your rules. This is the rule we recommend for google_maps_directions:
{
"version": "1",
"default": "deny",
"tools": {
"google_maps_directions": {}
}
}google_maps_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.
google_maps_directions. It is categorised as a Read tool in the Noapi Google Search MCP Server, which means it retrieves data without modifying state.
Register the Noapi Google Search MCP server in PolicyLayer and add a rule for google_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 Noapi Google Search. Nothing to install.
google_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 google_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 google_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.
google_maps_directions is provided by the Noapi Google Search MCP server (vincentkaufmann/noapi-google-search-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 38 Noapi Google Search tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
38 Noapi Google Search tools catalogued and risk-classified — across an index of 42,500+ MCP servers.