wmo-weather.forecast.daily
Get the official 7-day weather forecast for a city, sourced directly from that country's National Meteorological and Hydrological Service (NMHS) — the same forecast shown on the government weather portal, not a third-party model. Requires a WMO city ID (see wmo-weather.city_search first, e.g. 183...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/wmo-weather.forecast.daily.md
What wmo-weather.forecast.daily does on Apibase
AI agents use wmo-weather.forecast.daily to create or update resources in Apibase, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apibase environment.
| 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.forecast.daily is rated Medium
An AI agent can call wmo-weather.forecast.daily faster than any human can review: one bad instruction and it creates or modifies resources in Apibase by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs wmo-weather.forecast.daily 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.forecast.daily, this is the rule to start with:
wmo-weather.forecast.daily stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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.forecast.daily call is checked against it from then on.
Questions about wmo-weather.forecast.daily
Get the official 7-day weather forecast for a city, sourced directly from that country's National Meteorological and Hydrological Service (NMHS) — the same forecast shown on the government weather portal, not a third-party model. Requires a WMO city ID (see wmo-weather.city_search first, e.g. 183 for Tokyo). Returns daily min/max temperature and weather condition. Forecast coverage and update frequency vary by NMHS; some cities may return fewer days or none if the source NMHS has not published one. Data: worldweather.wmo.int, no auth required. It is categorised as a Write tool in the Apibase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
wmo-weather.forecast.daily 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.forecast.daily: 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.forecast.daily is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the wmo-weather.forecast.daily 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.forecast.daily. 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.forecast.daily 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