realestate_trend
Get the monthly time series of home values (ZHVI) or rents (ZORI) for a metro or state, to chart or analyze the trend.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/realestate-trend.md
What realestate_trend does on Livedatalink
AI agents call realestate_trend 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 |
|---|---|---|---|
metric | string | — | 'home_value' (ZHVI, default) or 'rent' (ZORI). |
months | number | — | How many recent months to return (default 24, max 360). |
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_trend is rated Low
This tool queries and returns time-series data about home values (ZHVI) and rental prices (ZORI) for geographic regions. It is a pure data retrieval operation with no side effects, no code execution, and no data modification. The stated purpose is analysis and charting, confirming read-only semantics. Misuse presents minimal risk as the data is descriptive market information.
From the tool's definition Tool description explicitly states 'Get the monthly time series' of real estate metrics 'to chart or analyze the trend' — retrieves historical data for analysis with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs realestate_trend 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_trend, this is the rule to start with:
realestate_trend 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_trend call is checked against it from then on.
Questions about realestate_trend
Get the monthly time series of home values (ZHVI) or rents (ZORI) for a metro or state, to chart or analyze the trend. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
realestate_trend accepts 3 parameters: metric, months, 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_trend: 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_trend 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_trend 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_trend. 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_trend 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