smhi.weather.observations
Get weather observations from a specific SMHI monitoring station in Sweden — current readings or time-series history (up to several months). SMHI operates 1000+ stations from southern Malmö to Abisko in the Arctic Circle. Stations measure different parameters: major airports (Stockholm-Arlanda, G...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/smhi.weather.observations.md
What smhi.weather.observations does on Apibase
AI agents call smhi.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 |
|---|---|---|---|
period | string | — | Time window for observations. "latest-hour" = most recent single reading. "latest-day" = last 24 hours with hourly readings (~25 values, default). "latest-month |
station_id | string | Yes | SMHI weather station ID (numeric string). Common examples: "97400" = Stockholm-Arlanda Flygplats, "98230" = Stockholm-Observatoriekullen A, "72630" = Göteborg, |
parameter_id | string | — | SMHI measurement parameter ID. Defaults to "1" (air temperature, °C, hourly). Common values: "1" = air temperature (°C), "4" = wind speed (m/s), "6" = relative |
Parameters from the server's own tool schema.
Why smhi.weather.observations is rated Low
Retrieves publicly available weather observation data with no side effects or data modification capabilities.
From the tool's definition Get weather observations from a specific SMHI monitoring station; current readings or time-series history
Attacks that exploit this kind of access
The rule that runs smhi.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 smhi.weather.observations, this is the rule to start with:
smhi.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 smhi.weather.observations call is checked against it from then on.
Questions about smhi.weather.observations
Get weather observations from a specific SMHI monitoring station in Sweden — current readings or time-series history (up to several months). SMHI operates 1000+ stations from southern Malmö to Abisko in the Arctic Circle. Stations measure different parameters: major airports (Stockholm-Arlanda, Göteborg-Landvetter) typically have temperature, wind, humidity, pressure, and visibility; automated rural stations may have just temperature and precipitation. Returns timestamp, numeric value, unit, and quality flag (G=approved, Y=provisional). Common station IDs: "97400" = Stockholm-Arlanda, "98230" = Stockholm-Observatoriekullen, "72630" = Göteborg, "61740" = Malmö, "188800" = Abisko (Lapland). Common parameter IDs: "1" = temperature (°C), "4" = wind speed (m/s), "6" = humidity (%), "9" = pressure (hPa), "39" = dew-point (°C). No API key required — SMHI open data, Creative Commons BY 4.0. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
smhi.weather.observations accepts 3 parameters: period, station_id, parameter_id. Required: station_id. 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 smhi.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.
smhi.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 smhi.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 smhi.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.
smhi.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