Verify the Zillow API connection and get server status.
AI agents call check_health to retrieve information from Zillow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a health/status check tool that queries the state of the API connection and server without retrieving user data, modifying records, executing external operations, or causing any side effects. It is purely informational and diagnostic in nature, making it a Read category tool with low severity.
From the tool's definition Tool name 'check_health' and description 'Verify the Zillow API connection and get server status' indicate status checking and diagnostic operations with no data retrieval, modification, or external actions.
Documented attack patterns abuse exactly the kind of access check_health gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zillow MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for check_health:
{
"version": "1",
"default": "deny",
"tools": {
"check_health": {}
}
}check_health is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Verify the Zillow API connection and get server status. It is categorised as a Read tool in the Zillow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zillow MCP Server MCP server in PolicyLayer and add a rule for check_health: 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 Zillow MCP Server. Nothing to install.
check_health 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 check_health 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 check_health. 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.
check_health is provided by the Zillow MCP Server MCP server (rohitsingh-iitd/zillow-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Zillow MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Zillow MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.