---
name: isopleth-hazards-read
description: Flood, wetland, wildfire and severe-weather exposure for one site, cited to FEMA, USFWS, USGS, NOAA and state fire-agency sources. Uses the Isopleth MCP server (https://api.isopleth.dev/mcp).
---

# Hazards Read

Flood, wetland, wildfire and severe-weather exposure for one site, cited to FEMA, USFWS, USGS, NOAA and state fire-agency sources.

## Requirements

- The Isopleth MCP server connected at `https://api.isopleth.dev/mcp` with an API key in the `Authorization: Bearer` header (see https://isopleth.dev/docs/mcp).
- Tools used: `fetch_location`, `fetch_batch`.
- Cost: 1 lookup per location (23 fields).

## Steps

1. Call fetch_location with the location, preset "flood_risk" and the extra hazard fields listed below.
2. Flood: report the FEMA flood zone (nfhl_flood_zone), whether the point is inside the mapped floodplain, coastal high-hazard status, elevation and distance to the coast.
3. Water and wetlands: say whether the point intersects a mapped wetland or water area, the wetland type, and how many wetlands are within 100 m and 500 m.
4. Fire and weather: report the fire hazard severity zone and the distance to the nearest past fire perimeter with its year (both from CAL FIRE, so mainly California), and the annual wildfire, tornado and hail frequencies (nationwide). Add the seismic design category and landslide susceptibility.
5. Keep "absent" (nothing mapped there) separate from "failed" (temporary). Never call a site safe because a field failed.

## Arguments

```json
{
  "preset": "flood_risk",
  "fields": [
    "nfhl_flood_zone",
    "coastal_high_hazard",
    "fire_hazard_severity_zone_class",
    "nearest_fire_perimeter_distance_m",
    "most_recent_burn_year",
    "wildfire_annual_frequency",
    "tornado_annual_frequency",
    "hail_annual_frequency",
    "seismic_design_category",
    "landslide_susceptibility_index"
  ]
}
```

## Output

A one-paragraph risk summary, then a table grouped as Flood, Water and wetlands, Fire, Weather and ground, each row with its source.

Every value carries its source, license and attribution. Keep the source next to each value, and show the attributions if you share the results.