realestate.property.details
Detailed property information by property ID — beds, baths, sqft, year built, lot size, tax assessment, HOA, days on market, photos, last sale price/date. Use for_sale search first to get property_id (RapidAPI / Realtor.com data)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/realestate.property.details.md
What realestate.property.details does on Apibase
AI agents call realestate.property.details to retrieve information from Apibase 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 | Property ID from a for_sale search result (e.g. "2734304997") |
Parameters from the server's own tool schema.
Why realestate.property.details is rated Low
Tool retrieves publicly available real estate property data with no modification or side effects.
From the tool's definition Detailed property information by property ID — beds, baths, sqft, year built, lot size
Attacks that exploit this kind of access
The rule that runs realestate.property.details safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For realestate.property.details, this is the rule to start with:
realestate.property.details 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 Apibase, apply this rule, and every realestate.property.details call is checked against it from then on.
Questions about realestate.property.details
Detailed property information by property ID — beds, baths, sqft, year built, lot size, tax assessment, HOA, days on market, photos, last sale price/date. Use for_sale search first to get property_id (RapidAPI / Realtor.com data). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
realestate.property.details 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 Apibase MCP server in PolicyLayer and add a rule for realestate.property.details: 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 Apibase. Nothing to install.
realestate.property.details 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 realestate.property.details 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 realestate.property.details. 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.
realestate.property.details is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue