weather_hourly
Get hourly weather forecast from Open-Meteo.
This record as markdown: /tools/creativelead-unclick/weather-hourly.md
What weather_hourly does on UnClick
AI agents call weather_hourly 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 |
|---|---|---|---|
days | number | — | |
latitude | number | — | |
timezone | string | — | |
longitude | number | — |
Parameters from the server's own tool schema.
Why weather_hourly is rated Low
This tool queries weather data and returns forecast information without creating, modifying, deleting, or executing any operations. It has no side effects and presents minimal security risk if misused by an AI agent, as weather data is public and non-sensitive. Classification as Read is appropriate.
From the tool's definition Tool retrieves hourly weather forecast data from Open-Meteo API. The verb 'Get' and the description indicating data retrieval with no modification capability indicate this is a read-only operation.
Attacks that exploit this kind of access
The rule that runs weather_hourly 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 weather_hourly, this is the rule to start with:
weather_hourly 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 weather_hourly call is checked against it from then on.
Questions about weather_hourly
Get hourly weather forecast from Open-Meteo. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
weather_hourly accepts 4 parameters: days, latitude, timezone, longitude. 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 weather_hourly: 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.
weather_hourly 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_hourly 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_hourly. 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_hourly is provided by the UnClick MCP server (creativelead/unclick). 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