Search places via Google Places Text Search
AI agents call search_places to retrieve information from Multi-MCPs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries the Google Places API to retrieve information about locations. It has no side effects, does not execute arbitrary code, does not modify data, and does not involve financial transactions. The low severity reflects minimal blast radius if misused by an AI agent—worst case would be excessive API calls or information gathering about locations.
From the tool's definition Tool name 'search_places' and description 'Search places via Google Places Text Search' indicate a query/search operation that retrieves place data without modifying or deleting anything.
Attacks that exploit this kind of access
Search places via Google Places Text Search. It is categorised as a Read tool in the Multi-MCPs MCP Server, which means it retrieves data without modifying state.
Register the Multi-MCPs MCP server in PolicyLayer and add a rule for 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 Multi-MCPs. Nothing to install.
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 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 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.
search_places is provided by the Multi-MCPs MCP server (taylorchen/muti-mcps). 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 →