wmo-weather.climate.normals
Get 30-year monthly climate normals for a city — average max/min/mean temperature and rainfall for each of the 12 months, sourced from the WMO climatological standard normals (typically 1961-1990 or 1991-2020 depending on the station). Requires a WMO city ID (see wmo-weather.city_search first, e....
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/wmo-weather.climate.normals.md
What wmo-weather.climate.normals does on Apibase
AI agents call wmo-weather.climate.normals to retrieve information from Apibase 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 |
|---|---|---|---|
city_id | integer | Yes | WMO city ID, e.g. 219 (Kabul) or 183 (Tokyo). Discover IDs with wmo-weather.city_search. |
Parameters from the server's own tool schema.
Why wmo-weather.climate.normals is rated Low
Retrieves historical climate data; no side effects, modifications, code execution, or financial transactions.
From the tool's definition Get 30-year monthly climate normals for a city — average max/min/mean temperature and rainfall
Attacks that exploit this kind of access
The rule that runs wmo-weather.climate.normals safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wmo-weather.climate.normals, this is the rule to start with:
wmo-weather.climate.normals 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 Apibase, apply this rule, and every wmo-weather.climate.normals call is checked against it from then on.
Questions about wmo-weather.climate.normals
Get 30-year monthly climate normals for a city — average max/min/mean temperature and rainfall for each of the 12 months, sourced from the WMO climatological standard normals (typically 1961-1990 or 1991-2020 depending on the station). Requires a WMO city ID (see wmo-weather.city_search first, e.g. 219 for Kabul). Useful for "what is the weather usually like in [city] in [month]" style questions, distinct from wmo-weather.forecast which covers the next 7 days. Data: worldweather.wmo.int, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
wmo-weather.climate.normals accepts 1 parameter: city_id. Required: city_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for wmo-weather.climate.normals: 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 Apibase. Nothing to install.
wmo-weather.climate.normals 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 wmo-weather.climate.normals 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 wmo-weather.climate.normals. 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.
wmo-weather.climate.normals is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue