Retrieve historical weather data for a specific month over multiple years. Returns monthly statistics including average, max, and min temperatures, total precipitation, and average wind speed. Default retrieves data for the past year, up to 10 years available. Accepts either city name OR latitude...
AI agents call get_historical_weather 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 queries and returns historical weather statistics (temperature, precipitation, wind speed) for a given location and time period. It has no side effects, does not modify any data, does not execute code or commands, and does not involve financial transactions. It is a straightforward read operation that retrieves pre-computed weather data from the Open-Meteo API.
From the tool's definition Tool 'retrieve[s]' historical weather data and 'Returns' statistics—no modification, deletion, or execution of external operations. Language indicates passive data retrieval only: 'Retrieve,' 'Returns,' no action verbs like 'execute,' 'delete,' or 'create.'
Attacks that exploit this kind of access
Retrieve historical weather data for a specific month over multiple years. Returns monthly statistics including average, max, and min temperatures, total precipitation, and average wind speed. Default retrieves data for the past year, up to 10 years available. Accepts either city name OR latitude/longitude coordinates. 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 get_historical_weather: 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.
get_historical_weather 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 get_historical_weather 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 get_historical_weather. 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.
get_historical_weather is provided by the Weather MCP Server MCP server (shayrylmae/weather-mcp-server). 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 →