AI agents call location_lookup to retrieve information from Attom without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Location lookup is fundamentally a read operation that retrieves information about geographic locations or properties without creating, modifying, or deleting any data. While the ATTOM API provides real estate data that could be sensitive (property addresses, valuations), the lookup itself is a passive query with minimal blast radius if misused—an agent could retrieve information but cannot modify records or trigger…
From the tool's definition Tool name 'location_lookup' and description 'Get location lookup information' indicate a retrieval operation with no modification of data. The function queries location/property data without side effects.
Attacks that exploit this kind of access
Get location lookup information. It is categorised as a Read tool in the Attom MCP Server, which means it retrieves data without modifying state.
Register the Attom MCP server in PolicyLayer and add a rule for location_lookup: 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 Attom. Nothing to install.
location_lookup 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 location_lookup 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 location_lookup. 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.
location_lookup is provided by the Attom MCP server (nkbud/mcp-server-attom). 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 →