metno.weather.alerts
Get all active weather alerts issued by the Norwegian Meteorological Institute for Norway. Alerts cover events such as gale, storm, heavy rain, snow, ice, avalanche, and fog. Each alert includes event type, awareness level (green/yellow/orange/red), severity, certainty, affected counties, descrip...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/metno.weather.alerts.md
What metno.weather.alerts does on Apibase
AI agents call metno.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 |
|---|---|---|---|
lang | string | — | Language for alert text. "en" = English (default), "no" = Norwegian. |
county | string | — | Filter alerts by Norwegian county name substring (e.g. "Oslo", "Viken", "Troms"). Case-insensitive partial match. |
event_type | string | — | Filter by event type slug (e.g. "wind", "rain", "snow", "ice", "fog", "avalanche"). Leave empty for all active alerts. |
Parameters from the server's own tool schema.
Why metno.weather.alerts is rated Low
Tool retrieves weather alert data with no side effects or operational impact.
From the tool's definition Get all active weather alerts; no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs metno.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 metno.weather.alerts, this is the rule to start with:
metno.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 metno.weather.alerts call is checked against it from then on.
Questions about metno.weather.alerts
Get all active weather alerts issued by the Norwegian Meteorological Institute for Norway. Alerts cover events such as gale, storm, heavy rain, snow, ice, avalanche, and fog. Each alert includes event type, awareness level (green/yellow/orange/red), severity, certainty, affected counties, description, consequences, and valid time interval. Filter by event type slug (wind, rain, snow, ice, fog, avalanche) or by county name. Returns English or Norwegian text. 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.alerts accepts 3 parameters: lang, county, event_type. 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.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.
metno.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 metno.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 metno.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.
metno.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