FEMA flood zone for a coordinate (lat/lon). Returns the FEMA flood zone code (AE, VE, X, …), Special-Flood-Hazard-Area flag (isSFHA — the 1% annual-chance floodplain where flood insurance is mandatory), a plain-language risk level + description, base flood elevation, and source FIRM panel. FEMA N...
AI agents call geo.flood-zone to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward geospatial data lookup tool that retrieves publicly available flood risk information. It has no side effects, does not modify any state, and poses minimal risk even if misused—the worst case is an AI agent returning inaccurate flood risk estimates, which is a data quality issue rather than a security or operational hazard.
From the tool's definition Tool returns FEMA flood zone data for a given coordinate (lat/lon): flood zone code, SFHA flag, risk level, base flood elevation, and FIRM panel source. All outputs are read-only informational queries against public FEMA databases (NFHL).
Attacks that exploit this kind of access
FEMA flood zone for a coordinate (lat/lon). Returns the FEMA flood zone code (AE, VE, X, …), Special-Flood-Hazard-Area flag (isSFHA — the 1% annual-chance floodplain where flood insurance is mandatory), a plain-language risk level + description, base flood elevation, and source FIRM panel. FEMA NFHL, free and keyless. 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 geo.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 Mcp. Nothing to install.
geo.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 geo.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 geo.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.
geo.flood-zone 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →