AI agents call get_planning_applications 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 and queries public planning application records. It has no side effects, does not modify data, does not execute external operations, and does not involve financial transactions. The read-only nature of searching planning records (typically public information in the UK) and the absence of any write, execute, or destructive capability clearly place it in the Read category with low severity.
From the tool's definition Tool description explicitly states 'Search planning applications' — a query operation with no modification or deletion capability. Returns historical planning data associated with property identifiers (UPRN).
Attacks that exploit this kind of access
Search planning applications associated with (or near) a UPRN. 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_planning_applications: 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_planning_applications 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_planning_applications 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_planning_applications. 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_planning_applications 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 →