Check FEMA National Flood Hazard Layer for any U.S. property. USE WHEN: user asks 'is this in a flood zone', 'do I need flood insurance', 'is this property flood-safe', 'FEMA flood map', 'is this in a 100-year flood plain', or mentions flood risk. RETURNS: FEMA zone code (X = low risk, A/AE = 100...
Part of the Buildability™ — Property Zoning & Buildability™ Intelligence server.
Free to start. No card required.
AI agents call check_flood_zone to retrieve information from Buildability™ — Property Zoning & Buildability™ Intelligence 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 check_flood_zone 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": {
"check_flood_zone": {}
}
}See the full Buildability™ — Property Zoning & Buildability™ Intelligence policy for all 8 tools.
These attack patterns abuse exactly the kind of access check_flood_zone 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.
Check FEMA National Flood Hazard Layer for any U.S. property. USE WHEN: user asks 'is this in a flood zone', 'do I need flood insurance', 'is this property flood-safe', 'FEMA flood map', 'is this in a 100-year flood plain', or mentions flood risk. RETURNS: FEMA zone code (X = low risk, A/AE = 100-year, V/VE = coastal high risk), flood insurance requirement (mandatory/optional), base flood elevation if applicable, and annual flood risk probability. Uses the official FEMA API.. It is categorised as a Read tool in the Buildability™ — Property Zoning & Buildability™ Intelligence MCP Server, which means it retrieves data without modifying state.
Register the Buildability™ — Property Zoning & Buildability™ Intelligence MCP server in PolicyLayer and add a rule for check_flood_zone: 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 Buildability™ — Property Zoning & Buildability™ Intelligence. Nothing to install.
check_flood_zone 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 check_flood_zone 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 check_flood_zone. 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.
check_flood_zone is provided by the Buildability™ — Property Zoning & Buildability™ Intelligence MCP server (https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Buildability™ — Property Zoning & Buildability™ Intelligence 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.