gov.hazard-mitigation
FEMA Hazard Mitigation Assistance (HMA) funded projects — the pre- and post-disaster mitigation grants FEMA has actually obligated (HMGP, BRIC/PDM, FMA). Filter by state (2-letter), disasterNumber, programFy (fiscal year), and/or programArea; at least one filter required. Returns total matching p...
This record as markdown: /tools/io-github-2s-io-mcp/gov.hazard-mitigation.md
What gov.hazard-mitigation does on Mcp
AI agents call gov.hazard-mitigation to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why gov.hazard-mitigation is rated Low
This is a pure data retrieval tool that queries publicly available FEMA datasets. It allows filtering and searching existing records but does not create, modify, delete, or execute any operations. The data returned is public-domain government information with no side effects or state changes. No financial transactions, code execution, or destructive operations are possible.
From the tool's definition Returns FEMA Hazard Mitigation Assistance project data filtered by state, disaster number, fiscal year, and program area.
Attacks that exploit this kind of access
The rule that runs gov.hazard-mitigation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gov.hazard-mitigation, this is the rule to start with:
gov.hazard-mitigation 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 Mcp, apply this rule, and every gov.hazard-mitigation call is checked against it from then on.
Questions about gov.hazard-mitigation
FEMA Hazard Mitigation Assistance (HMA) funded projects — the pre- and post-disaster mitigation grants FEMA has actually obligated (HMGP, BRIC/PDM, FMA). Filter by state (2-letter), disasterNumber, programFy (fiscal year), and/or programArea; at least one filter required. Returns total matching project count + projects (identifier, program area, project type, status, recipient/subrecipient, county, project amount + federal share obligated USD, cost-share %, benefit-cost ratio, number of properties, approval/close dates), largest federal share first. Free, public-domain (OpenFEMA). Distinct from gov.public-assistance (recovery grants) and gov.nfip-claims (flood losses) — this is mitigation funding to reduce future risk. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for gov.hazard-mitigation: 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 Mcp. Nothing to install.
gov.hazard-mitigation 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 gov.hazard-mitigation 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 gov.hazard-mitigation. 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.
gov.hazard-mitigation is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue