Search for places using Google Places API
AI agents call maps_search_places to retrieve information from Server Puppeteer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a search operation (a classic Read action) against Google Places API. It retrieves location data in response to a query. There is no indication of data modification, code execution, deletion, or financial transactions.
From the tool's definition Tool description states 'Search for places using Google Places API' — a read-only query operation that retrieves place data without modifying, executing code, or triggering external side effects beyond data retrieval.
Attacks that exploit this kind of access
Search for places using Google Places API. It is categorised as a Read tool in the Server Puppeteer MCP Server, which means it retrieves data without modifying state.
Register the Server Puppeteer MCP server in PolicyLayer and add a rule for maps_search_places: 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 Server Puppeteer. Nothing to install.
maps_search_places 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 maps_search_places 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 maps_search_places. 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.
maps_search_places is provided by the Server Puppeteer MCP server (@hisma/server-puppeteer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →