fema_nfhl_search_inventory

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp

Low RISK CLASS

Category Read

Parameters 110 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/fema-nfhl-search-inventory.md

WHAT IT DOES

What fema_nfhl_search_inventory does on Livedatalink

AI agents call fema_nfhl_search_inventory 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
`sort`	string	—	Stable sort. Default jurisdiction.
`limit`	integer	—	Maximum rows. Default 20.
`query`	string	—	DFIRM ID, item ID, jurisdiction, state, code, or filename search terms (maximum 8 terms).
`state`	string	—	Two-letter state/territory code or full FEMA state name.
`offset`	integer	—	Rows to skip. Default 0.
`updated_from`	string	—	Inclusive displayed inventory update date floor, YYYY-MM-DD.
`response_format`	string	—	Human-readable markdown or machine-readable JSON. Default markdown.
`updated_through`	string	—	Inclusive displayed inventory update date ceiling, YYYY-MM-DD.
`jurisdiction_kind`	string	—	Inventory coverage-unit kind derived conservatively from FEMA identifiers/names.
`max_advertised_mb`	number	—	Maximum FEMA-advertised package size in approximate MiB.
`min_advertised_mb`	number	—	Minimum FEMA-advertised package size in approximate MiB.

Parameters from the server's own tool schema.

RISK

Why fema_nfhl_search_inventory is rated Low

Even though fema_nfhl_search_inventory 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.

Risk signalsHigh parameter count (11 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs fema_nfhl_search_inventory 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_search_inventory, this is the rule to start with:

fema_nfhl_search_inventory Allowed

fema_nfhl_search_inventory 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": {
    "fema_nfhl_search_inventory": {}
  }
}

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

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

FAQ

Questions about fema_nfhl_search_inventory

What does the fema_nfhl_search_inventory tool do? +

Search LiveDataLink's complete pinned projection of FEMA's nationwide NFHL coverage/download inventory by jurisdiction, state, unit kind, displayed update date, and advertised ZIP size. Returns bounded pagination, both displayed and filename-derived dates, canonical FEMA download evidence, and snapshot hashes. Commercial use: screen coverage/freshness and plan acquisition before property diligence. This is inventory metadata only; for an address or coordinate flood-zone question use flood_zone_lookup, which consults FEMA's live Flood Hazard Zones layer. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

What parameters does fema_nfhl_search_inventory accept? +

fema_nfhl_search_inventory accepts 11 parameters: sort, limit, query, state, offset, updated_from, response_format, updated_through, jurisdiction_kind, max_advertised_mb, min_advertised_mb. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on fema_nfhl_search_inventory? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for fema_nfhl_search_inventory: 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.

What risk level is fema_nfhl_search_inventory? +

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

Can I rate-limit fema_nfhl_search_inventory? +

Yes. Add a rate_limit block to the fema_nfhl_search_inventory 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 fema_nfhl_search_inventory completely? +

Set action: deny in the PolicyLayer policy for fema_nfhl_search_inventory. 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 fema_nfhl_search_inventory? +

fema_nfhl_search_inventory 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.

KEEP EXPLORING

More on Livedatalink, and thousands of servers like it.

This server

All 381 Livedatalink tools →

Across the catalogue

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

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