smhi.weather.fire_risk

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 32 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/smhi.weather.fire-risk.md

WHAT IT DOES

What smhi.weather.fire_risk does on Apibase

AI agents call smhi.weather.fire_risk 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	—	Forecast period granularity. "daily" = 7 daily steps (default, recommended for planning). "hourly" = sub-daily steps with higher temporal resolution.
`latitude`	number	Yes	Latitude in decimal degrees for the location in Sweden (55–70°N). Examples: 59.3293 = Stockholm, 55.6050 = Malmö, 65.5848 = Sundsvall.
`longitude`	number	Yes	Longitude in decimal degrees for the location in Sweden (10–30°E). Examples: 18.0686 = Stockholm, 13.0038 = Malmö, 17.3102 = Sundsvall.

Parameters from the server's own tool schema.

RISK

Why smhi.weather.fire_risk is rated Low

Read-only weather forecast retrieval with no side effects.

From the tool's definition Get the 7-day daily fire weather risk forecast

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs smhi.weather.fire_risk 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.fire_risk, this is the rule to start with:

smhi.weather.fire_risk Allowed

smhi.weather.fire_risk is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "smhi.weather.fire_risk": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every smhi.weather.fire_risk call is checked against it from then on.

FAQ

Questions about smhi.weather.fire_risk

What does the smhi.weather.fire_risk tool do? +

Get the 7-day daily fire weather risk forecast for a location in Sweden from SMHI. Provides the Canadian Forest Fire Weather Index (FWI) system adapted for Swedish conditions. Returns per-day values for: fwiindex (composite fire danger 1–6 scale), grassfire (grass fire risk 1–6), forestdry (forest drought index), fwi (Fire Weather Index), isi (Initial Spread Index), bui (Build-Up Index), ffmc (Fine Fuel Moisture Code), dmc (Duff Moisture Code), dc (Drought Code), plus weather inputs: t (temperature °C), ws (wind speed m/s), wd (wind direction °), r (relative humidity %), and accumulated precipitation over 1/2/3/5/7/10/14/20/30/40/50/60 days. fwiindex scale: 1=Very low, 2=Low, 3=Moderate, 4=High, 5=Very high, 6=Extreme. Covers Sweden only (lat 55–70°N, lon 10–30°E). 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.

What parameters does smhi.weather.fire_risk accept? +

smhi.weather.fire_risk accepts 3 parameters: period, latitude, longitude. Required: latitude, longitude. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on smhi.weather.fire_risk? +

Register the Apibase MCP server in PolicyLayer and add a rule for smhi.weather.fire_risk: 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.

What risk level is smhi.weather.fire_risk? +

smhi.weather.fire_risk is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit smhi.weather.fire_risk? +

Yes. Add a rate_limit block to the smhi.weather.fire_risk 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.

How do I block smhi.weather.fire_risk completely? +

Set action: deny in the PolicyLayer policy for smhi.weather.fire_risk. 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.

What MCP server provides smhi.weather.fire_risk? +

smhi.weather.fire_risk 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.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

aiva_get_churn_risk on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →