nfip_flood_claims
National Flood Insurance Program claim history aggregated by zip, county, or state. Useful for insurance brokers and homebuyers assessing prior loss patterns.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/nfip-flood-claims.md
What nfip_flood_claims does on Livedatalink
AI agents call nfip_flood_claims 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 |
|---|---|---|---|
zip | string | — | Five-digit zip code. |
limit | number | — | Max rows (default 200). |
state | string | — | Two-letter state code. |
county | string | — | FEMA county code. |
end_year | number | — | Latest year of loss. |
start_year | number | — | Earliest year of loss. |
Parameters from the server's own tool schema.
Why nfip_flood_claims is rated Low
Even though nfip_flood_claims 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 nfip_flood_claims 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 nfip_flood_claims, this is the rule to start with:
nfip_flood_claims 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 nfip_flood_claims call is checked against it from then on.
Questions about nfip_flood_claims
National Flood Insurance Program claim history aggregated by zip, county, or state. Useful for insurance brokers and homebuyers assessing prior loss patterns. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
nfip_flood_claims accepts 6 parameters: zip, limit, state, county, end_year, start_year. 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 nfip_flood_claims: 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.
nfip_flood_claims 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 nfip_flood_claims 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 nfip_flood_claims. 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.
nfip_flood_claims 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