AI agents call search_property_listings to retrieve information from Homedata without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and server context strongly suggest this retrieves or queries property listing information without modifying data. This fits the 'Read' category. While the empty description introduces some ambiguity, the consistent pattern across sibling tools and the 'search' verb (typical for retrieval) support a Read classification with medium-high confidence.
From the tool's definition Tool name 'search_property_listings' indicates retrieval of property listing data. Server context shows this is a query-focused API for UK property information (EPCs, sale history, planning, etc.).
Attacks that exploit this kind of access
search_property_listings. It is categorised as a Read tool in the Homedata MCP Server, which means it retrieves data without modifying state.
Register the Homedata MCP server in PolicyLayer and add a rule for search_property_listings: 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 Homedata. Nothing to install.
search_property_listings 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 search_property_listings 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 search_property_listings. 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.
search_property_listings is provided by the Homedata MCP server (wehomemove/homedata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →