weather_search_location
AI agents call weather_search_location to retrieve information from Weather MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches/queries location data to support weather lookups—a read-only operation with no side effects, data modification, or execution risk. The empty description prevents full certainty, but the naming pattern and server context strongly indicate a simple lookup function.
From the tool's definition Tool name 'weather_search_location' and sibling tools (weather_get_current, weather_get_forecast, weather_get_hourly) all perform data retrieval operations. Server description states it 'Provides weather data' with no modifications or deletions.
Attacks that exploit this kind of access
weather_search_location. It is categorised as a Read tool in the Weather MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Weather MCP Server MCP server in PolicyLayer and add a rule for weather_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 MCP Server. Nothing to install.
weather_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 weather_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 weather_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.
weather_search_location is provided by the Weather MCP Server MCP server (skyloevil/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 →