Get aggregated Census demographics for radius rings around a US property address — the standard 1/3/5-mile trade-area format used in CRE site analysis. Aggregates every census tract whose centroid falls within each radius: population, household-weighted median income, employment rate, college att...
AI agents call get_radius_demographics 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 |
|---|---|---|---|
address | string | Yes | Full US property address (e.g. "1234 Main St, Charlotte, NC 28202") |
radii_miles | string | — | Comma-separated radii in miles (default "1,3,5", each capped at 15) |
Parameters from the server's own tool schema.
This tool performs passive data retrieval from Census data sources. It reads publicly available demographic information and aggregates it for analysis purposes. There is no capability to modify, delete, execute code, or create financial obligations. The data returned informs site analysis decisions but does not itself alter any system state.
From the tool's definition Tool retrieves aggregated Census demographics data (population, income, employment, housing metrics) for specified radius rings around a property address.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get aggregated Census demographics for radius rings around a US property address — the standard 1/3/5-mile trade-area format used in CRE site analysis. Aggregates every census tract whose centroid falls within each radius: population, household-weighted median income, employment rate, college attainment, housing vacancy, renter share, and median rent. Use this for trade-area / site analysis. Use get_market_demographics for the single census tract immediately around the address. It is categorised as a Read tool in the CRE Intelligence MCP MCP Server, which means it retrieves data without modifying state.
get_radius_demographics accepts 2 parameters: address, radii_miles. Required: address. 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 get_radius_demographics: 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.
get_radius_demographics 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 get_radius_demographics 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 get_radius_demographics. 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.
get_radius_demographics 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 →