AI agents call lookup_property_core 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.
This tool retrieves property information from the Homedata API without modifying data. It is classified as Read because it queries and returns data about UK properties. Severity is medium rather than low because property data can include sensitive personal information (council tax, planning applications, crime statistics, demographics) that could be misused for stalking, discrimination, or privacy violations if an…
From the tool's definition Tool name 'lookup_property_core' combined with server context describing 'query UK property data including EPCs, sale history, planning, flood risk, council tax, demographics' indicates a data retrieval operation.
Attacks that exploit this kind of access
lookup_property_core. 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 lookup_property_core: 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.
lookup_property_core 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 lookup_property_core 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 lookup_property_core. 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.
lookup_property_core 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 →