AI agents call lookup_flood_risk 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 queries and returns pre-existing flood risk information. It has no side effects, does not modify data, execute code, delete records, or involve financial transactions. The blast radius of misuse is minimal—an AI agent could retrieve flood risk data for properties it shouldn't access (privacy concern), but this is a data access control issue rather than a tool capability issue.
From the tool's definition Tool retrieves flood risk classification data from Environment Agency for a property. No modification, deletion, or execution of commands occurs. The verb 'Get' and the context of querying existing data confirm read-only functionality.
Attacks that exploit this kind of access
Get Environment Agency flood risk classification 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 lookup_flood_risk: 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_flood_risk 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_flood_risk 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_flood_risk. 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_flood_risk 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 →