AI agents call search_places to retrieve information from LatLng without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
lat | number | — | Optional latitude to bias results. |
lon | number | — | Optional longitude to bias results. |
type | string | — | Optional place category, for example restaurant or cafe. |
limit | integer | — | |
query | string | Yes | Place name or search query. |
country | string | — | Optional country code, for example US. |
Parameters from the server's own tool schema.
This tool retrieves place information based on search criteria (name, location bias, category filter) without creating, modifying, deleting, or executing any operations. It is a pure query/retrieval function with no side effects, fitting the Read category. Severity is low because geocoding data exposure has minimal impact on security or privacy in most contexts.
From the tool's definition Tool description states 'Search for places by name' with optional biasing parameters. The verb 'search' and the read-only nature of querying a places database with no modification or execution capability.
Attacks that exploit this kind of access
Search for places by name, optionally biased by location and category. It is categorised as a Read tool in the LatLng MCP Server, which means it retrieves data without modifying state.
search_places accepts 6 parameters: lat, lon, type, limit, query, country. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the LatLng 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 LatLng. 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 LatLng MCP server (https://mcp.latlng.work/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
search_places is one line of LatLng's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →