census_income_housing

Median household income, per capita income, housing units, owner vs renter occupancy, median home value, median gross and contract rent for a US geography. Used for real estate AI, market analysis, location-based pricing.

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp
Low RISK CLASS
Category Read
Parameters 81 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/census-income-housing.md

What census_income_housing does on Livedatalink

AI agents call census_income_housing 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.

ParameterTypeRequiredDescription
msa string 5-digit Metropolitan Statistical Area code. Required for msa level.
year number ACS 5-year endpoint year (default 2023).
zcta string 5-digit ZIP Code Tabulation Area. Required for zcta level.
level string Yes Geography level: 'us', 'state', 'county', 'zcta' (ZIP), 'place' (city), 'tract', 'msa'.
place string Census place FIPS (city). Required for place level.
state string 2-letter state code (e.g. 'TX') or 2-digit FIPS. Required for state/county/place/tract levels.
tract string 6-digit census tract code. Use '*' for all tracts in a county.
county string 3-digit county FIPS. Use '*' for all counties in a state. Required for county/tract levels.

Parameters from the server's own tool schema.

Why census_income_housing is rated Low

This is a pure data retrieval tool that queries census statistics. It has no side effects—it does not create, modify, delete, or execute anything. The use cases mentioned ('real estate AI, market analysis, location-based pricing') are read-only analytical tasks. Severity is low because exposure of census data carries minimal direct risk; it is public demographic information.

From the tool's definition Tool retrieves demographic and housing statistics (median income, housing units, occupancy, home values, rent) for US geographies. No description indicates modification, deletion, or execution of code/commands.

Questions about census_income_housing

What does the census_income_housing tool do? +

Median household income, per capita income, housing units, owner vs renter occupancy, median home value, median gross and contract rent for a US geography. Used for real estate AI, market analysis, location-based pricing. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

What parameters does census_income_housing accept? +

census_income_housing accepts 8 parameters: msa, year, zcta, level, place, state, tract, county. Required: level. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on census_income_housing? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for census_income_housing: 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.

What risk level is census_income_housing? +

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

Can I rate-limit census_income_housing? +

Yes. Add a rate_limit block to the census_income_housing 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 census_income_housing completely? +

Set action: deny in the PolicyLayer policy for census_income_housing. 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 census_income_housing? +

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

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Livedatalink's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.