historical_weather
Get historical daily weather data for a location from Open-Meteo archive (1940 to 5 days ago).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/historical-weather.md
What historical_weather does on UnClick
AI agents call historical_weather to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
end_date | string | Yes | End date in YYYY-MM-DD format. |
latitude | number | Yes | Latitude of the location. |
longitude | number | Yes | Longitude of the location. |
start_date | string | Yes | Start date in YYYY-MM-DD format. |
Parameters from the server's own tool schema.
Why historical_weather is rated Low
This tool purely retrieves historical weather information without creating, modifying, deleting, or executing any operations. It has no side effects and does not access sensitive or restricted data. The blast radius of misuse is minimal—an agent could only query historical weather data unnecessarily or retrieve data for unintended locations, causing no harm.
From the tool's definition Tool description states 'Get historical daily weather data' which is a retrieval operation with no modification or side effects. The data source is a public weather archive (Open-Meteo) covering historical periods (1940 to 5 days ago).
Attacks that exploit this kind of access
The rule that runs historical_weather safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For historical_weather, this is the rule to start with:
historical_weather is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every historical_weather call is checked against it from then on.
Questions about historical_weather
Get historical daily weather data for a location from Open-Meteo archive (1940 to 5 days ago). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
historical_weather accepts 4 parameters: end_date, latitude, longitude, start_date. Required: end_date, latitude, longitude, start_date. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for 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 UnClick. Nothing to install.
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 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 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.
historical_weather is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue