Screen a US county as a LAND-INVESTING market (raw-land flip / Podolsky style). Grades the county on the signals that matter for buying cheap rural land and reselling on terms: population growth, demographics, owner share, and affordability. IMPORTANT: This screens on FREE Census data only (growt...
AI agents call screen_land_market 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 |
|---|---|---|---|
state | string | Yes | 2-letter state abbreviation (e.g. "AZ") or 2-digit state FIPS |
county | string | Yes | County name (e.g. "Mohave" or "Mohave County") |
Parameters from the server's own tool schema.
This tool retrieves and analyzes publicly available Census data to produce market rankings. It has no side effects on the user's systems or external data sources. The explicit warning that it should not be used for actual purchase decisions underscores that it is informational (Read category) rather than operational.
From the tool's definition Tool description states it 'screens' and 'grades' using 'FREE Census data only' and explicitly does NOT access 'actual land sale prices or comps.' The function is to 'rank/shortlist markets' by querying public demographic and growth signals.
Attacks that exploit this kind of access
Screen a US county as a LAND-INVESTING market (raw-land flip / Podolsky style). Grades the county on the signals that matter for buying cheap rural land and reselling on terms: population growth, demographics, owner share, and affordability. IMPORTANT: This screens on FREE Census data only (growth + demographics + a home-value affordability proxy). It does NOT include actual land sale prices or comps — those require county records or a paid service, and must be verified per-parcel before buying. Use this to rank/shortlist markets, not to buy. It is categorised as a Read tool in the CRE Intelligence MCP MCP Server, which means it retrieves data without modifying state.
screen_land_market accepts 2 parameters: state, county. Required: state, county. 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_land_market: 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_land_market 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_land_market 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_land_market. 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_land_market 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 →