Search for locations matching query.
AI agents call weather_search to retrieve information from Weather without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns location data matching user input. It retrieves information without creating, modifying, deleting, or executing any operations. The search operation is read-only and has no adverse impact even if called arbitrarily by an AI agent.
From the tool's definition Tool name is 'weather_search' and description states 'Search for locations matching query' — a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access weather_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Weather, and nothing reaches the server without passing your rules. This is the rule we recommend for weather_search:
{
"version": "1",
"default": "deny",
"tools": {
"weather_search": {}
}
}weather_search 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 locations matching query. It is categorised as a Read tool in the Weather MCP Server, which means it retrieves data without modifying state.
Register the Weather MCP server in PolicyLayer and add a rule for weather_search: 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. Nothing to install.
weather_search 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 weather_search 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 weather_search. 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.
weather_search is provided by the Weather MCP server (sjanax01/weather-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Weather, 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.
9 Weather tools catalogued and risk-classified — across an index of 43,000+ MCP servers.