Search for GPS coordinates of a city or location by name using Open-Meteo geocoding API. Examples: - Search for Paris: {
AI agents call search_location to retrieve information from MCP Weather Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only lookup of geographic coordinates using the Open-Meteo geocoding API. It queries external data and returns results without creating, modifying, deleting, or executing any operations. The tool has no destructive, financial, or execution capabilities. Even if misused by an AI agent, it only retrieves publicly available location data with no blast radius.
From the tool's definition Tool name 'search_location' and description 'Search for GPS coordinates of a city or location by name' indicate a query operation that retrieves location data without modification or side effects.
Documented attack patterns abuse exactly the kind of access search_location gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Weather Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_location:
{
"version": "1",
"default": "deny",
"tools": {
"search_location": {}
}
}search_location is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search for GPS coordinates of a city or location by name using Open-Meteo geocoding API. Examples: - Search for Paris: {. It is categorised as a Read tool in the MCP Weather Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Weather 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 MCP Weather 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 MCP Weather Server MCP server (tjarriault/mcp-weather-sample). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Weather Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 MCP Weather Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.