brightsky.weather.observations
Get hourly weather observations or forecast for any location in Germany from DWD (Deutscher Wetterdienst). Pass a past date to retrieve historical observations; pass a future date to retrieve the DWD numerical forecast. Each hour includes: temperature, dew point, humidity, pressure, cloud cover, ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/brightsky.weather.observations.md
What brightsky.weather.observations does on Apibase
AI agents call brightsky.weather.observations 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 |
|---|---|---|---|
date | string | Yes | Start date/time for observations in ISO 8601 format (e.g. "2026-07-01" or "2026-07-01T08:00:00"). Returns historical data when date is in the past; returns DWD |
units | string | — | Unit system: "dwd" (default) uses km/h wind and °C temperature; "si" uses m/s wind |
latitude | number | Yes | Latitude of the location in Germany (e.g. 52.52 for Berlin, range 47–56) |
last_date | string | — | End date/time for observations in ISO 8601 format. When omitted, returns data for the 24-hour period starting at "date". Maximum range is 10 days. |
longitude | number | Yes | Longitude of the location in Germany (e.g. 13.40 for Berlin, range 5–16) |
Parameters from the server's own tool schema.
Why brightsky.weather.observations is rated Low
Retrieves historical or forecast weather data without modifying state or executing operations.
From the tool's definition Get hourly weather observations or forecast for any location in Germany from DWD
Attacks that exploit this kind of access
The rule that runs brightsky.weather.observations 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 brightsky.weather.observations, this is the rule to start with:
brightsky.weather.observations 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 brightsky.weather.observations call is checked against it from then on.
Questions about brightsky.weather.observations
Get hourly weather observations or forecast for any location in Germany from DWD (Deutscher Wetterdienst). Pass a past date to retrieve historical observations; pass a future date to retrieve the DWD numerical forecast. Each hour includes: temperature, dew point, humidity, pressure, cloud cover, visibility, precipitation, sunshine, wind speed/direction, wind gusts, precipitation probability, solar irradiance, and condition icon. Returns up to 10 days of data (240 hourly records). No API key required — open DWD data via Bright Sky (MIT licence). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
brightsky.weather.observations accepts 5 parameters: date, units, latitude, last_date, longitude. Required: date, latitude, longitude. 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 brightsky.weather.observations: 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.
brightsky.weather.observations 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 brightsky.weather.observations 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 brightsky.weather.observations. 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.
brightsky.weather.observations 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