realestate_home_values
Get the typical home value for a metro or state (Zillow Home Value Index): the latest value plus 1-year and 5-year-ago values and percent change. Pass a region name or id.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/realestate-home-values.md
What realestate_home_values does on Livedatalink
AI agents call realestate_home_values 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_home_values is rated Low
This tool retrieves historical and current real estate pricing data from the Zillow Home Value Index. It performs a read-only query operation with no ability to modify, delete, or execute code. The data returned is informational and publicly available market data. There is no financial transaction, data modification, or destructive capability.
From the tool's definition Tool description states 'Get the typical home value' and 'retrieve...the latest value plus 1-year and 5-year-ago values and percent change.' These are query/retrieval operations with no side effects.
Attacks that exploit this kind of access
The rule that runs realestate_home_values 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_home_values, this is the rule to start with:
realestate_home_values 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_home_values call is checked against it from then on.
Questions about realestate_home_values
Get the typical home value for a metro or state (Zillow Home Value Index): the latest value plus 1-year and 5-year-ago values and percent change. Pass a region name or id. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
realestate_home_values 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_home_values: 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_home_values 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_home_values 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_home_values. 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_home_values 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