"Housing market trends in [ZIP]" / "median home price in [area]" / "is [ZIP] heating up or cooling" / "sales volume in [neighborhood]" — aggregated real estate market trends by ZIP. Returns average/median sale price, sales volume, and price changes monthly / quarterly / yearly across a date range...
Part of the Attom server.
Free to start. No card required.
AI agents call attom_sales_trend to retrieve information from Attom without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though attom_sales_trend only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"attom_sales_trend": {}
}
}See the full Attom policy for all 28 tools.
These attack patterns abuse exactly the kind of access attom_sales_trend gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
"Housing market trends in [ZIP]" / "median home price in [area]" / "is [ZIP] heating up or cooling" / "sales volume in [neighborhood]" — aggregated real estate market trends by ZIP. Returns average/median sale price, sales volume, and price changes monthly / quarterly / yearly across a date range. Use for market-direction questions before pulling individual addresses.. 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 attom_sales_trend: 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.
attom_sales_trend 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 attom_sales_trend 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 attom_sales_trend. 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.
attom_sales_trend is provided by the Attom MCP server (https://gateway.pipeworx.io/attom/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 28 Attom tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.