google-maps.place_details
Get detailed information for a Google Maps place. Provide place_id from search results. The identifier also accepts the business identifier form (0x...:0x...). Optional region and language are supported. Returns a flat place object with fields such as name, full_address, location, hours, status, ...
This record as markdown: /tools/io-github-vee3io-vee3/google-maps.place-details.md
What google-maps.place_details does on Vee3
AI agents call google-maps.place_details 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 |
|---|---|---|---|
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). |
place_id | string | Yes | Google Maps place identifier (for example ChIJk_grnPDq9EcRE7gOH9gAPZA). Also accepts the business identifier form (for example 0x47f4eb87e91f866d:0x9629fabb993e |
Parameters from the server's own tool schema.
Why google-maps.place_details is rated Low
This tool retrieves and queries publicly available place information from Google Maps without side effects. It accepts read-only parameters (place_id, optional region and language) and returns descriptive data. There is no indication of data modification, deletion, code execution, or financial operations.
From the tool's definition Tool description states it 'Get detailed information' and 'Returns a flat place object with fields such as name, full_address, location, hours, status, rating, review_count, website, phone_number, and types' — purely informational retrieval with no…
Attacks that exploit this kind of access
The rule that runs google-maps.place_details 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.place_details, this is the rule to start with:
google-maps.place_details 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.place_details call is checked against it from then on.
Questions about google-maps.place_details
Get detailed information for a Google Maps place. Provide place_id from search results. The identifier also accepts the business identifier form (0x...:0x...). Optional region and language are supported. Returns a flat place object with fields such as name, full_address, location, hours, status, rating, review_count, website, phone_number, and types when available. Additional upstream fields may appear. Cost = 4 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
google-maps.place_details accepts 3 parameters: region, language, place_id. Required: place_id. 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.place_details: 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.place_details 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.place_details 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.place_details. 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.place_details 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