AI agents call all_events_detail 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 is a Read operation—it retrieves and queries property event data without side effects. Severity is medium rather than low because the tool accesses detailed real estate information that could include sensitive property transaction histories, ownership records, or financial valuations that might be misused for privacy invasion, stalking, or discriminatory targeting if called at scale by an agent without proper…
From the tool's definition Tool name 'all_events_detail' and description 'Get all events detail information' indicate a retrieval/query operation with no modification. The ATTOM real estate API context confirms this retrieves historical event data about properties.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get all events detail 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 all_events_detail: 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.
all_events_detail 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 all_events_detail 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 all_events_detail. 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.
all_events_detail 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 →