AI agents call get_property_sales 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 sales history data from HM Land Registry, which is publicly available historical information. It performs no mutations, deletions, or external operations—only data retrieval. While access to property information could have privacy implications in some contexts, the data queried is from public land registry records. The impact is read-only with no reversible or irreversible side effects.
From the tool's definition Tool name 'get_property_sales' and description 'Return the full HM Land Registry sale history for a property' indicate retrieval of historical data without modification or deletion. The action is a query/fetch operation on existing public property records.
Attacks that exploit this kind of access
Return the full HM Land Registry sale history for a property. 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 get_property_sales: 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.
get_property_sales 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 get_property_sales 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 get_property_sales. 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.
get_property_sales 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 →