google-maps.search
Search Google Maps by text query. Optional filters include location, radius (defaults to 1000 meters), open_now, min_price, max_price, place_type, language, and region. Pass cursor from a previous cursor_next to fetch the next page. Returns matching places in places with names, full_address, plac...
This record as markdown: /tools/io-github-vee3io-vee3/google-maps.search.md
What google-maps.search does on Vee3
AI agents call google-maps.search to retrieve information from Vee3 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Search query for places (for example restaurants in Paris). |
cursor | object | — | Pagination cursor from cursor_next on a previous response. |
radius | object | — | Search radius in meters (default 1000). |
region | object | — | Two-character region code (for example us). On search endpoints this biases results by ccTLD. On place endpoints this selects regional place data. |
language | object | — | Language code for results (for example en). |
location | object | — | Optional latitude and longitude bias point (for example 40,-110). A location embedded in the query may override this. |
open_now | object | — | When true, return only places open for business at query time. |
max_price | object | — | Maximum price level (0–4, inclusive). |
min_price | object | — | Minimum price level (0–4, inclusive). |
place_type | object | — | Restrict results to a single Google Maps place type (for example restaurant). |
Parameters from the server's own tool schema.
Why google-maps.search is rated Low
This is a read-only query tool that retrieves and returns public map search results. The filtering options (location, price range, place type, language) are all query parameters that shape what data is retrieved, not modify or destroy data. The pagination mechanism (cursor_next/cursor_previous) is standard for retrieving additional results. No side effects, financial impact, or destructive actions are possible.
From the tool's definition Tool description states "Search Google Maps by text query" with optional filters and returns matching places data (names, addresses, ratings, location). No modification, deletion, or code execution described.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs google-maps.search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For google-maps.search, this is the rule to start with:
google-maps.search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Vee3, apply this rule, and every google-maps.search call is checked against it from then on.
Questions about google-maps.search
Search Google Maps by text query. Optional filters include location, radius (defaults to 1000 meters), open_now, min_price, max_price, place_type, language, and region. Pass cursor from a previous cursor_next to fetch the next page. Returns matching places in places with names, full_address, place_id, ratings, and location. Use place_id with place detail, review, and photo endpoints. cursor_next and cursor_previous appear only when pagination cursors are available. Additional upstream fields may appear. Cost = 10 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
google-maps.search accepts 10 parameters: query, cursor, radius, region, language, location, open_now, max_price, min_price, place_type. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Vee3 MCP server in PolicyLayer and add a rule for google-maps.search: 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 Vee3. Nothing to install.
google-maps.search 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.search 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.search. 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.search is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vee3, and thousands of servers like it.
This server
Across the catalogue