realestate_market_screen
Get a read-only market screen for a metro or state: latest Zillow typical home value (ZHVI) and asking rent (ZORI), with 1-year and 5-year changes where available. Returns market context only, not a parcel record, comparable sale, owner/title result, appraisal, score, or investment decision.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/realestate-market-screen.md
What realestate_market_screen does on Livedatalink
AI agents call realestate_market_screen 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 |
|---|---|---|---|
region | string | Yes | Metro or state name (e.g. 'Austin, TX', 'Houston', 'Texas') or a Zillow region id. |
Parameters from the server's own tool schema.
Why realestate_market_screen is rated Low
Even though realestate_market_screen 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 realestate_market_screen 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 realestate_market_screen, this is the rule to start with:
realestate_market_screen 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 realestate_market_screen call is checked against it from then on.
Questions about realestate_market_screen
Get a read-only market screen for a metro or state: latest Zillow typical home value (ZHVI) and asking rent (ZORI), with 1-year and 5-year changes where available. Returns market context only, not a parcel record, comparable sale, owner/title result, appraisal, score, or investment decision. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
realestate_market_screen accepts 1 parameter: region. Required: region. 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 realestate_market_screen: 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.
realestate_market_screen 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 realestate_market_screen 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 realestate_market_screen. 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.
realestate_market_screen 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