geo.flood-zone

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...

SERVERMcp SOURCE@2sio/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-2s-io-mcp/geo.flood-zone.md

WHAT IT DOES

What geo.flood-zone does on Mcp

AI agents call geo.flood-zone 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.

RISK

Why geo.flood-zone is rated Low

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

RECOMMENDED RULE

The rule that runs geo.flood-zone 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 geo.flood-zone, this is the rule to start with:

geo.flood-zone Allowed

geo.flood-zone is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "geo.flood-zone": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every geo.flood-zone call is checked against it from then on.

FAQ

Questions about geo.flood-zone

What does the geo.flood-zone tool do? +

How do I enforce a policy on geo.flood-zone? +

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.

What risk level is geo.flood-zone? +

geo.flood-zone is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit geo.flood-zone? +

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.

How do I block geo.flood-zone completely? +

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.

What MCP server provides geo.flood-zone? +

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.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 572 tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →