Get historical weather data for a specific location and date range
AI agents call get_historical_weather to retrieve information from Open Meteo 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 retrieves historical weather data. It performs a read-only operation with no side effects, no code execution, no data modification, and no destructive actions. The tool fits squarely within the Read category as it simply fetches existing data based on location and date parameters.
From the tool's definition Tool name is 'get_historical_weather' and description states 'Get historical weather data for a specific location and date range' — this is a retrieval operation with no modification, deletion, or execution of external commands.
Attacks that exploit this kind of access
Get historical weather data for a specific location and date range. It is categorised as a Read tool in the Open Meteo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Open Meteo 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 Open Meteo 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 Open Meteo MCP Server MCP server (sarthakray26/open-meteo-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 →