realestate_status

Report real-estate store coverage: number of regions, total monthly data points, the latest month available, and last refresh. Data is Zillow Research (ZHVI + ZORI), metro and state level.

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/realestate-status.md

WHAT IT DOES

What realestate_status does on Livedatalink

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

RISK

Why realestate_status is rated Low

The tool retrieves and displays informational status about real-estate data availability and refresh timing. It performs no writes, deletions, code execution, or financial transactions. The blast radius of misuse is minimal—an agent could only waste time querying status information repeatedly.

From the tool's definition Tool description indicates it 'Report[s]' coverage metrics: 'number of regions, total monthly data points, the latest month available, and last refresh.' These are read-only status/metadata queries with no modification, deletion, or execution of external…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs realestate_status 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_status, this is the rule to start with:

realestate_status Allowed

realestate_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "realestate_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every realestate_status call is checked against it from then on.

FAQ

Questions about realestate_status

What does the realestate_status tool do? +

Report real-estate store coverage: number of regions, total monthly data points, the latest month available, and last refresh. Data is Zillow Research (ZHVI + ZORI), metro and state level. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on realestate_status? +

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

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

Can I rate-limit realestate_status? +

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

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

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

KEEP EXPLORING

More on Livedatalink, and thousands of servers like it.

This server

All 280 Livedatalink tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →