fema_nfhl_get_inventory_item
Get one self-hosted FEMA NFHL inventory unit by exact DFIRM ID. Returns jurisdiction, state, coverage-unit kind, package update date, advertised size, filename, canonical FEMA download URL, and immutable provenance. Use this to produce acquisition evidence after search. It does not fetch or inspe...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/fema-nfhl-get-inventory-item.md
What fema_nfhl_get_inventory_item does on Livedatalink
AI agents call fema_nfhl_get_inventory_item to retrieve information from Livedatalink 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 |
|---|---|---|---|
dfirm_id | string | Yes | Exact six-character FEMA DFIRM ID, optionally suffixed -NFHL. |
response_format | string | — | Human-readable markdown or machine-readable JSON. Default markdown. |
Parameters from the server's own tool schema.
Why fema_nfhl_get_inventory_item is rated Low
Even though fema_nfhl_get_inventory_item only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs fema_nfhl_get_inventory_item safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fema_nfhl_get_inventory_item, this is the rule to start with:
fema_nfhl_get_inventory_item 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 Livedatalink, apply this rule, and every fema_nfhl_get_inventory_item call is checked against it from then on.
Questions about fema_nfhl_get_inventory_item
Get one self-hosted FEMA NFHL inventory unit by exact DFIRM ID. Returns jurisdiction, state, coverage-unit kind, package update date, advertised size, filename, canonical FEMA download URL, and immutable provenance. Use this to produce acquisition evidence after search. It does not fetch or inspect the geodatabase; use flood_zone_lookup for address/coordinate zone questions. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
fema_nfhl_get_inventory_item accepts 2 parameters: dfirm_id, response_format. Required: dfirm_id. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for fema_nfhl_get_inventory_item: 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 Livedatalink. Nothing to install.
fema_nfhl_get_inventory_item 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 fema_nfhl_get_inventory_item 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 fema_nfhl_get_inventory_item. 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.
fema_nfhl_get_inventory_item is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue