fema.disaster.assistance
Query federal disaster housing assistance data by state and disaster number. Returns registration counts, average damage, total inspected, approved amounts by county. Useful for disaster recovery analysis and aid distribution research. Source: OpenFEMA.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/fema.disaster.assistance.md
What fema.disaster.assistance does on Apibase
AI agents call fema.disaster.assistance 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 |
|---|---|---|---|
limit | integer | — | Number of results (1-50, default 10) |
state | string | Yes | US state code (e.g. TX, FL, CA) |
disaster_number | integer | — | FEMA disaster number to filter (e.g. 4673) |
Parameters from the server's own tool schema.
Why fema.disaster.assistance is rated Low
Tool queries public disaster assistance data with no mutation, execution, or financial impact capabilities.
From the tool's definition Query federal disaster housing assistance data by state and disaster number. Returns registration counts, average damage, total inspected, approved amounts.
Attacks that exploit this kind of access
The rule that runs fema.disaster.assistance 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.assistance, this is the rule to start with:
fema.disaster.assistance 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.assistance call is checked against it from then on.
Questions about fema.disaster.assistance
Query federal disaster housing assistance data by state and disaster number. Returns registration counts, average damage, total inspected, approved amounts by county. Useful for disaster recovery analysis and aid distribution research. Source: OpenFEMA. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
fema.disaster.assistance accepts 3 parameters: limit, state, disaster_number. Required: state. 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.assistance: 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.assistance 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.assistance 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.assistance. 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.assistance 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