parcel_sales_history
Get the recorded sale history (price + date, no party names) for one parcel by account id. Useful for valuation, appreciation, and comp analysis.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/parcel-sales-history.md
What parcel_sales_history does on Livedatalink
AI agents call parcel_sales_history to retrieve information from Livedatalink 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 |
|---|---|---|---|
state | string | — | 2-letter state code. Coverage: 'MD' (Maryland statewide) or 'TX' (Harris County / Houston only). Defaults to MD. |
account_id | string | Yes | Parcel account id (from parcel_search). |
Parameters from the server's own tool schema.
Why parcel_sales_history is rated Low
This tool retrieves historical real estate sales data for analysis purposes. It performs a straightforward query operation with no side effects, no data modification, and no execution of external commands. The read-only nature and limited data scope (price and date only) make this a low-severity Read operation.
From the tool's definition Tool description states it 'Get[s] the recorded sale history (price + date, no party names) for one parcel by account id.' The action is purely retrieval of historical data with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs parcel_sales_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For parcel_sales_history, this is the rule to start with:
parcel_sales_history 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 Livedatalink, apply this rule, and every parcel_sales_history call is checked against it from then on.
Questions about parcel_sales_history
Get the recorded sale history (price + date, no party names) for one parcel by account id. Useful for valuation, appreciation, and comp analysis. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
parcel_sales_history accepts 2 parameters: state, account_id. Required: account_id. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for parcel_sales_history: 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 Livedatalink. Nothing to install.
parcel_sales_history 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 parcel_sales_history 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 parcel_sales_history. 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.
parcel_sales_history is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue