google-maps.review_details
Get details for one Google Maps review. Provide review_id from a place reviews response. Returns one review object at the top level with fields such as review_id, review_text, rating, and user_name when available. Additional upstream fields may appear. Cost = 2 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/google-maps.review-details.md
What google-maps.review_details does on Vee3
AI agents call google-maps.review_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 |
|---|---|---|---|
review_id | string | Yes | Google Maps review identifier. |
Parameters from the server's own tool schema.
Why google-maps.review_details is rated Low
This tool retrieves publicly available review information from Google Maps without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that queries existing data. The low severity reflects minimal security risk—review details are publicly accessible information, and misuse would only allow viewing data already visible to the public.
From the tool's definition Tool description states 'Get details for one Google Maps review' and 'Returns one review object' with fields like review_id, review_text, rating, and user_name.
Attacks that exploit this kind of access
The rule that runs google-maps.review_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.review_details, this is the rule to start with:
google-maps.review_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.review_details call is checked against it from then on.
Questions about google-maps.review_details
Get details for one Google Maps review. Provide review_id from a place reviews response. Returns one review object at the top level with fields such as review_id, review_text, rating, and user_name when available. Additional upstream fields may appear. Cost = 2 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
google-maps.review_details accepts 1 parameter: review_id. Required: review_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.review_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.review_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.review_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.review_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.review_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