Search for places using Google Places API
AI agents call maps_search_places to retrieve information from Helm Chart CLI without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search query against Google Places API to retrieve place information. It has no side effects—it does not create, modify, delete, or execute arbitrary code. The operation is purely read-based data retrieval with minimal blast radius if misused (e.g., excessive API calls, PII leakage from place details).
From the tool's definition Tool name 'maps_search_places' and description 'Search for places using Google Places API' indicate a query operation that retrieves location data without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
Search for places using Google Places API. It is categorised as a Read tool in the Helm Chart CLI MCP Server, which means it retrieves data without modifying state.
Register the Helm Chart CLI 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 Helm Chart CLI. 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 Helm Chart CLI MCP server (jeff-nasseri/servers). 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 →