brightsky.weather.current
Get current weather conditions for any location in Germany from the nearest DWD (Deutscher Wetterdienst) station. Returns: temperature (°C), humidity, dew point, pressure (hPa), cloud cover, visibility, wind speed/direction, wind gusts, precipitation in the last 10/30/60 minutes, sunshine duratio...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/brightsky.weather.current.md
What brightsky.weather.current does on Apibase
AI agents call brightsky.weather.current 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 |
|---|---|---|---|
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) |
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.current is rated Low
Retrieves real-time weather data with no side effects or ability to modify state.
From the tool's definition Get current weather conditions for any location in Germany from nearest DWD station.
Attacks that exploit this kind of access
The rule that runs brightsky.weather.current 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.current, this is the rule to start with:
brightsky.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 Apibase, apply this rule, and every brightsky.weather.current call is checked against it from then on.
Questions about brightsky.weather.current
Get current weather conditions for any location in Germany from the nearest DWD (Deutscher Wetterdienst) station. Returns: temperature (°C), humidity, dew point, pressure (hPa), cloud cover, visibility, wind speed/direction, wind gusts, precipitation in the last 10/30/60 minutes, sunshine duration, solar radiation, and weather condition (dry, fog, rain, sleet, snow, hail, thunderstorm). Source: official German Weather Service real-time observations. Coverage: Germany only. 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.current accepts 3 parameters: units, latitude, longitude. Required: 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.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 Apibase. Nothing to install.
brightsky.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 brightsky.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 brightsky.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.
brightsky.weather.current 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