AI agents call geoid_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.
This tool retrieves geographic identifier information from the ATTOM real estate API. It performs a read-only lookup operation with no side effects, no code execution, no data modification, and no destructive actions. The blast radius of misuse is minimal—an agent could retrieve geographic IDs but cannot modify data or trigger external operations.
From the tool's definition Tool name 'geoid_lookup' and description 'Get geographic ID lookup information' indicate data retrieval with no modification or execution. The verb 'Get' and 'lookup' are query operations that retrieve reference data.
Attacks that exploit this kind of access
Get geographic ID 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 geoid_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.
geoid_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 geoid_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 geoid_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.
geoid_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 →