brightsky.weather.alerts
Get active DWD (Deutscher Wetterdienst) severe weather alerts and warnings for any location in Germany. Identifies the warn cell (administrative district) for the given coordinates and returns all current alerts with: event type (e.g. thunderstorm, heavy rain, frost, storm), severity (Minor/Moder...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/brightsky.weather.alerts.md
What brightsky.weather.alerts does on Apibase
AI agents call brightsky.weather.alerts 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 |
|---|---|---|---|
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.alerts is rated Low
Retrieves weather alert data from public DWD source; no modifications, deletions, or external state changes.
From the tool's definition Get active DWD severe weather alerts and warnings for any location in Germany.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs brightsky.weather.alerts 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.alerts, this is the rule to start with:
brightsky.weather.alerts 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.alerts call is checked against it from then on.
Questions about brightsky.weather.alerts
Get active DWD (Deutscher Wetterdienst) severe weather alerts and warnings for any location in Germany. Identifies the warn cell (administrative district) for the given coordinates and returns all current alerts with: event type (e.g. thunderstorm, heavy rain, frost, storm), severity (Minor/Moderate/Severe/Extreme), urgency, certainty, onset/expiry times, headline, description, and recommended action in English. Returns an empty list when no warnings are active. 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.alerts accepts 2 parameters: 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.alerts: 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.alerts 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.alerts 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.alerts. 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.alerts 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