weather_current
Get current weather for a location from Open-Meteo (no API key required).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/weather-current.md
What weather_current does on UnClick
AI agents call weather_current 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 |
|---|---|---|---|
latitude | number | Yes | |
timezone | string | — | |
longitude | number | Yes |
Parameters from the server's own tool schema.
Why weather_current is rated Low
This tool retrieves current weather information from Open-Meteo without making any modifications, creating deletions, executing arbitrary code, or initiating financial transactions. It is a simple query operation that returns data, making it a Read category risk. Severity is low because misuse would only expose publicly available weather data with no blast radius or harmful consequences.
From the tool's definition Tool description states 'Get current weather for a location' which is a retrieval operation with no side effects. The use of 'Get' and the read-only nature of querying weather data confirms this is a data retrieval function.
Attacks that exploit this kind of access
The rule that runs weather_current 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_current, this is the rule to start with:
weather_current 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_current call is checked against it from then on.
Questions about weather_current
Get current weather for a location from Open-Meteo (no API key required). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
weather_current accepts 3 parameters: latitude, timezone, longitude. Required: latitude, 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_current: 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_current 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_current 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_current. 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_current 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