fema.disaster.declarations
Search US federal disaster declarations from 1953 to present. Filter by state, incident type (Fire, Flood, Hurricane, Tornado, Earthquake), and year. Returns disaster number, title, dates, designated programs (IA, PA, HM). Source: OpenFEMA (US Gov open data).
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/fema.disaster.declarations.md
What fema.disaster.declarations does on Apibase
AI agents call fema.disaster.declarations to retrieve information from Apibase 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 |
|---|---|---|---|
year | integer | — | Filter by declaration year (1953-2026) |
limit | integer | — | Number of results (1-50, default 10) |
state | string | — | US state code (e.g. CA, TX, FL). Omit for all states. |
incident_type | string | — | Disaster type to filter (e.g. Fire, Flood, Hurricane) |
Parameters from the server's own tool schema.
Why fema.disaster.declarations is rated Low
Queries historical disaster declaration data from public government sources with no side effects.
From the tool's definition Search US federal disaster declarations, filter by state, incident type, year. Returns data.
Attacks that exploit this kind of access
The rule that runs fema.disaster.declarations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fema.disaster.declarations, this is the rule to start with:
fema.disaster.declarations 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 Apibase, apply this rule, and every fema.disaster.declarations call is checked against it from then on.
Questions about fema.disaster.declarations
Search US federal disaster declarations from 1953 to present. Filter by state, incident type (Fire, Flood, Hurricane, Tornado, Earthquake), and year. Returns disaster number, title, dates, designated programs (IA, PA, HM). Source: OpenFEMA (US Gov open data). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
fema.disaster.declarations accepts 4 parameters: year, limit, state, incident_type. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for fema.disaster.declarations: 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 Apibase. Nothing to install.
fema.disaster.declarations 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.disaster.declarations 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.disaster.declarations. 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.disaster.declarations is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue