metno.weather.forecast
Get a 9-day (216-hour) hourly weather forecast for any global lat/lon point from the Norwegian Meteorological Institute Locationforecast 2.0 model. Returns air temperature, wind speed/direction/gusts, cloud cover, humidity, pressure, UV index, precipitation amounts and probability, and symbolic w...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/metno.weather.forecast.md
What metno.weather.forecast does on Apibase
AI agents call metno.weather.forecast 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 |
|---|---|---|---|
lat | number | Yes | Latitude in decimal degrees (e.g. 59.91 for Oslo, -33.87 for Sydney) |
lon | number | Yes | Longitude in decimal degrees (e.g. 10.75 for Oslo, 151.21 for Sydney) |
hours | integer | — | Number of hourly forecast entries to return (1–216, default 48). Full 9-day range = 216. |
altitude | integer | — | Station altitude in metres above sea level. Improves pressure correction. |
Parameters from the server's own tool schema.
Why metno.weather.forecast is rated Low
Tool retrieves meteorological data with no side effects, mutations, or external state changes.
From the tool's definition Get...weather forecast for any global lat/lon point...Returns air temperature, wind speed, cloud cover, humidity, pressure.
Attacks that exploit this kind of access
The rule that runs metno.weather.forecast 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 metno.weather.forecast, this is the rule to start with:
metno.weather.forecast 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 metno.weather.forecast call is checked against it from then on.
Questions about metno.weather.forecast
Get a 9-day (216-hour) hourly weather forecast for any global lat/lon point from the Norwegian Meteorological Institute Locationforecast 2.0 model. Returns air temperature, wind speed/direction/gusts, cloud cover, humidity, pressure, UV index, precipitation amounts and probability, and symbolic weather codes (e.g. clearsky_day, rain). Global coverage. CC BY 4.0 + NLOD 2.0, no auth, no upstream cost. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
metno.weather.forecast accepts 4 parameters: lat, lon, hours, altitude. Required: lat, lon. 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 metno.weather.forecast: 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.
metno.weather.forecast 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 metno.weather.forecast 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 metno.weather.forecast. 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.
metno.weather.forecast 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