disaster_history_summary
Multi-year FEMA disaster summary for a location. Buckets declarations by incident type and year so insurance brokers and realtors can assess cumulative risk on the same address used in property_lookup.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/disaster-history-summary.md
What disaster_history_summary does on Livedatalink
AI agents call disaster_history_summary 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 code. |
years | number | — | Lookback window in years (default 10). |
county | string | — | County name. |
Parameters from the server's own tool schema.
Why disaster_history_summary is rated Low
This tool queries and returns historical disaster information for a given location. It performs data retrieval with no side effects, reversibility concerns, code execution, destructive operations, or financial implications. The use case (insurance brokers and realtors assessing risk) is informational.
From the tool's definition Tool description states it 'summarizes' and 'buckets declarations' — retrieval and aggregation of historical disaster data. No modification, execution, deletion, or financial transaction occurs.
Attacks that exploit this kind of access
The rule that runs disaster_history_summary 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 disaster_history_summary, this is the rule to start with:
disaster_history_summary 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 disaster_history_summary call is checked against it from then on.
Questions about disaster_history_summary
Multi-year FEMA disaster summary for a location. Buckets declarations by incident type and year so insurance brokers and realtors can assess cumulative risk on the same address used in property_lookup. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
disaster_history_summary accepts 3 parameters: state, years, county. 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 disaster_history_summary: 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.
disaster_history_summary 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 disaster_history_summary 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 disaster_history_summary. 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.
disaster_history_summary 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