google-maps.nearby_search
Search for places near a latitude and longitude. Required: location. Optional: radius (defaults to 1000 meters when sort_by is Relevance), keyword, place_type, open_now, min_price, max_price, language, region, and cursor. When sort_by is Distance, omit radius and provide keyword or place_type. Pa...
This record as markdown: /tools/io-github-vee3io-vee3/google-maps.nearby-search.md
What google-maps.nearby_search does on Vee3
AI agents call google-maps.nearby_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 |
|---|---|---|---|
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. |
keyword | object | — | Keyword to match nearby places (for example restaurant). |
sort_by | object | — | Result ordering: "Relevance" (default) or "Distance". |
language | object | — | Language code for results (for example en). |
location | string | Yes | Latitude and longitude of the search point (for example 40,-110). |
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.nearby_search is rated Low
This tool performs a read-only query against Google Maps data. It searches and retrieves information about nearby places based on geographic coordinates and optional filters. There are no side effects, no data modification, no code execution, and no financial impact. The tool simply returns matching place information that can be used with other endpoints.
From the tool's definition Tool description states 'Search for places near a latitude and longitude' and 'Returns matching places in places'. The function retrieves publicly available location data without modifying, deleting, or executing operations.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs google-maps.nearby_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.nearby_search, this is the rule to start with:
google-maps.nearby_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.nearby_search call is checked against it from then on.
Questions about google-maps.nearby_search
Search for places near a latitude and longitude. Required: location. Optional: radius (defaults to 1000 meters when sort_by is Relevance), keyword, place_type, open_now, min_price, max_price, language, region, and cursor. When sort_by is Distance, omit radius and provide keyword or place_type. Pass cursor from a previous cursor_next to fetch the next page. Returns matching places in places. 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.nearby_search accepts 11 parameters: cursor, radius, region, keyword, sort_by, language, location, open_now, max_price, min_price, place_type. Required: location. 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.nearby_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.nearby_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.nearby_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.nearby_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.nearby_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