Get FEMA disaster declarations filtered by state, year, or type. Returns federal disaster declarations including major disasters, emergencies, and fire management assistance. Each record includes the disaster number, title, declaration date, and affected area. Args: state: Two-letter US state abb...
Part of the FEMA Disasters server.
Free to start. No card required.
AI agents call get_disaster_declarations to retrieve information from FEMA Disasters without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_disaster_declarations only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_disaster_declarations": {}
}
}See the full FEMA Disasters policy for all 5 tools.
These attack patterns abuse exactly the kind of access get_disaster_declarations gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Get FEMA disaster declarations filtered by state, year, or type. Returns federal disaster declarations including major disasters, emergencies, and fire management assistance. Each record includes the disaster number, title, declaration date, and affected area. Args: state: Two-letter US state abbreviation (e.g. 'CA', 'TX', 'FL'). year: Filter by fiscal year of the declaration (e.g. 2023). disaster_type: Declaration type code: 'DR' (major disaster), 'EM' (emergency), or 'FM' (fire management assistance). limit: Maximum number of records to return (default 25, max 1000).. It is categorised as a Read tool in the FEMA Disasters MCP Server, which means it retrieves data without modifying state.
Register the FEMA Disasters MCP server in PolicyLayer and add a rule for get_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 FEMA Disasters. Nothing to install.
get_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 get_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 get_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.
get_disaster_declarations is provided by the FEMA Disasters MCP server (https://mcp.olyport.com/fema/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 FEMA Disasters tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.