realestate_search
Find real-estate markets (metro areas or states) by name and get each one's latest typical home value (Zillow Home Value Index). Use this to discover the region name/id before calling realestate_home_values, realestate_rents, or realestate_trend.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/realestate-search.md
What realestate_search does on Livedatalink
AI agents call realestate_search 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 |
|---|---|---|---|
type | string | — | Optional filter: 'metro' or 'state'. |
limit | number | — | Max rows (default 10, max 50). |
query | string | Yes | Name fragment, e.g. 'Austin', 'Bay Area', 'Texas'. |
Parameters from the server's own tool schema.
Why realestate_search is rated Low
This tool retrieves real estate market data and pricing information without creating, modifying, deleting, or executing any operations. It is a read-only query function that searches and returns existing data from the Zillow Home Value Index. The blast radius of misuse is minimal—an agent might retrieve irrelevant market data but cannot cause financial harm, delete data, or trigger external actions.
From the tool's definition Tool performs search and discovery operations to 'Find real-estate markets' and 'get each one's latest typical home value' - data retrieval with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs realestate_search 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_search, this is the rule to start with:
realestate_search 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_search call is checked against it from then on.
Questions about realestate_search
Find real-estate markets (metro areas or states) by name and get each one's latest typical home value (Zillow Home Value Index). Use this to discover the region name/id before calling realestate_home_values, realestate_rents, or realestate_trend. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
realestate_search accepts 3 parameters: type, limit, query. Required: query. 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_search: 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_search 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_search 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_search. 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_search 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