fema_nfhl_summarize_state_inventory
Summarize all hosted FEMA NFHL inventory units for one state/territory: unit counts by kind, oldest/latest package dates, total advertised download-volume estimate, and largest unit. Use for state coverage/freshness comparisons and data-acquisition budgeting. This does not mean every place or par...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/fema-nfhl-summarize-state-inventory.md
What fema_nfhl_summarize_state_inventory does on Livedatalink
AI agents call fema_nfhl_summarize_state_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 |
|---|---|---|---|
state | string | Yes | Two-letter state/territory code or full FEMA state name. |
response_format | string | — | Human-readable markdown or machine-readable JSON. Default markdown. |
Parameters from the server's own tool schema.
Why fema_nfhl_summarize_state_inventory is rated Low
Even though fema_nfhl_summarize_state_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 signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs fema_nfhl_summarize_state_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_summarize_state_inventory, this is the rule to start with:
fema_nfhl_summarize_state_inventory 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_summarize_state_inventory call is checked against it from then on.
Questions about fema_nfhl_summarize_state_inventory
Summarize all hosted FEMA NFHL inventory units for one state/territory: unit counts by kind, oldest/latest package dates, total advertised download-volume estimate, and largest unit. Use for state coverage/freshness comparisons and data-acquisition budgeting. This does not mean every place or parcel has digital NFHL geometry and is not a flood determination. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
fema_nfhl_summarize_state_inventory accepts 2 parameters: state, response_format. Required: state. 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_summarize_state_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.
fema_nfhl_summarize_state_inventory 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_summarize_state_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.
Set action: deny in the PolicyLayer policy for fema_nfhl_summarize_state_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.
fema_nfhl_summarize_state_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.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue