fema_nfhl_get_snapshot_metadata
Return the pinned FEMA NFHL inventory snapshot's run ID, row/state counts, displayed update-date coverage, hashes, acquisition method/evidence origin, rights, exact official source URLs, scope boundary, fail-closed inventory-schema checks, and MapServer layer-ID/type verification. Use this to qua...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/fema-nfhl-get-snapshot-metadata.md
What fema_nfhl_get_snapshot_metadata does on Livedatalink
AI agents call fema_nfhl_get_snapshot_metadata to retrieve information from Livedatalink without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
response_format | string | — | Human-readable markdown or machine-readable JSON. Default markdown. |
Parameters from the server's own tool schema.
Why fema_nfhl_get_snapshot_metadata is rated Low
Even though fema_nfhl_get_snapshot_metadata only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs fema_nfhl_get_snapshot_metadata safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fema_nfhl_get_snapshot_metadata, this is the rule to start with:
fema_nfhl_get_snapshot_metadata 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 Livedatalink, apply this rule, and every fema_nfhl_get_snapshot_metadata call is checked against it from then on.
Questions about fema_nfhl_get_snapshot_metadata
Return the pinned FEMA NFHL inventory snapshot's run ID, row/state counts, displayed update-date coverage, hashes, acquisition method/evidence origin, rights, exact official source URLs, scope boundary, fail-closed inventory-schema checks, and MapServer layer-ID/type verification. Use this to qualify evidence and freshness before relying on inventory results. This is not a polygon corpus and does not replace flood_zone_lookup. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
fema_nfhl_get_snapshot_metadata accepts 1 parameter: response_format. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for fema_nfhl_get_snapshot_metadata: 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 Livedatalink. Nothing to install.
fema_nfhl_get_snapshot_metadata 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 fema_nfhl_get_snapshot_metadata 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 fema_nfhl_get_snapshot_metadata. 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.
fema_nfhl_get_snapshot_metadata is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue