redfin_estimate
Get Redfin Estimate. Returns the Redfin Estimate for a property, including the current estimate, property facts, and the monthly estimate history with city/county/postal comparatives. Faithful pass-through of Redfin's public avm + avmHistoricalData resources.
This record as markdown: /tools/crawlora-mcp/redfin-estimate.md
What redfin_estimate does on Crawlora
AI agents call redfin_estimate to retrieve information from Crawlora without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
property_id | string | Yes | Redfin property id |
Parameters from the server's own tool schema.
Why redfin_estimate is rated Low
This tool retrieves publicly available property valuation data from Redfin's public APIs. It performs a read-only query operation with no capability to modify, delete, or execute code. The data returned is informational (estimates, facts, historical data). No destructive, financial transaction, or system execution risks are present.
From the tool's definition Tool description states it 'Returns the Redfin Estimate for a property, including the current estimate, property facts, and the monthly estimate history' and is a 'Faithful pass-through of Redfin's public avm + avmHistoricalData resources.' The verbs…
Attacks that exploit this kind of access
The rule that runs redfin_estimate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For redfin_estimate, this is the rule to start with:
redfin_estimate is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crawlora, apply this rule, and every redfin_estimate call is checked against it from then on.
Questions about redfin_estimate
Get Redfin Estimate. Returns the Redfin Estimate for a property, including the current estimate, property facts, and the monthly estimate history with city/county/postal comparatives. Faithful pass-through of Redfin's public avm + avmHistoricalData resources. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
redfin_estimate accepts 1 parameter: property_id. Required: property_id. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for redfin_estimate: 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 Crawlora. Nothing to install.
redfin_estimate 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 redfin_estimate 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 redfin_estimate. 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.
redfin_estimate is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue