Pre-screen a land parcel's location for the AUTOMATABLE due-diligence red flags: FEMA flood zone and federal wetlands. Pulls live from FEMA's National Flood Hazard Layer and the US Fish & Wildlife National Wetlands Inventory. Use this to kill obviously-bad parcels (flood zone, wetlands) at scale ...
AI agents call screen_parcel_dd to retrieve information from CRE Intelligence MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
lat | number | Yes | Parcel latitude (decimal degrees) |
lng | number | Yes | Parcel longitude (decimal degrees) |
Parameters from the server's own tool schema.
This tool retrieves/queries external public data sources (FEMA NFHL and USFWS NWI) to screen a parcel for flood zone and wetland flags. It has no side effects — it reads and returns data only. Severity is medium because misclassification of a parcel (false clean result) could lead to a poor real estate investment decision, but the tool itself causes no direct harm and explicitly warns of its limitations.
From the tool's definition Pulls live from FEMA's National Flood Hazard Layer and the US Fish & Wildlife National Wetlands Inventory
Attacks that exploit this kind of access
Pre-screen a land parcel's location for the AUTOMATABLE due-diligence red flags: FEMA flood zone and federal wetlands. Pulls live from FEMA's National Flood Hazard Layer and the US Fish & Wildlife National Wetlands Inventory. Use this to kill obviously-bad parcels (flood zone, wetlands) at scale BEFORE spending time on manual due diligence. IMPORTANT: Checks flood + wetlands only. It does NOT check legal ACCESS (landlocked — the #1 land deal-killer), title/liens, or zoning — those stay MANUAL, per-parcel checks via county records. A clean screen here is necessary, NOT sufficient. It is categorised as a Read tool in the CRE Intelligence MCP MCP Server, which means it retrieves data without modifying state.
screen_parcel_dd accepts 2 parameters: lat, lng. Required: lat, lng. The full parameter table on this page comes from the server's own tool schema.
Register the CRE Intelligence MCP server in PolicyLayer and add a rule for screen_parcel_dd: 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 CRE Intelligence MCP. Nothing to install.
screen_parcel_dd 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 screen_parcel_dd 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 screen_parcel_dd. 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.
screen_parcel_dd is provided by the CRE Intelligence MCP server (Zwondra/cre-intelligence-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 →