Search for locations by name to get coordinates for weather queries. Uses Nominatim (OpenStreetMap) for excellent coverage of cities, towns, villages, and hamlets worldwide. Use this when the user provides a location name instead of coordinates (e.g., "Paris", "New York", "Tokyo", "San Francisco,...
AI agents call search_location to retrieve information from Weather Data MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Maximum number of results to return (1-100, default: 5) |
query | string | Yes | Location name to search for (e.g., "Paris", "New York, NY", "Tokyo") |
Parameters from the server's own tool schema.
This tool performs a simple geocoding lookup—converting a location name into coordinates and metadata. It retrieves information from a third-party API without creating, modifying, or deleting any data. There are no side effects, no code execution on the user's system, and no financial implications.
From the tool's definition The tool "search_location" retrieves location data by querying the Nominatim (OpenStreetMap) API. The description explicitly states it "Returns location matches with coordinates, timezone, elevation, and other metadata" without any modification or deletion of…
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Search for locations by name to get coordinates for weather queries. Uses Nominatim (OpenStreetMap) for excellent coverage of cities, towns, villages, and hamlets worldwide. Use this when the user provides a location name instead of coordinates (e.g., "Paris", "New York", "Tokyo", "San Francisco, CA", "Small Village, County"). Returns location matches with coordinates, timezone, elevation, and other metadata. Enables natural language location queries like "What's the weather in Paris?" by converting location names to coordinates. It is categorised as a Read tool in the Weather Data MCP Server MCP Server, which means it retrieves data without modifying state.
search_location accepts 2 parameters: limit, query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Weather Data MCP Server MCP server in PolicyLayer and add a rule for search_location: 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 Weather Data MCP Server. Nothing to install.
search_location 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_location 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_location. 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_location is provided by the Weather Data MCP Server MCP server (@dangahagan/weather-mcp). 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 →