property_value_history
Get property value history and tax assessment trends over multiple years. Shows year-by-year market value, land value, improvement value, and percentage change. Use this for questions like "how has this property's value changed?", "what's the appreciation rate?", "show me the tax assessment histo...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/property-value-history.md
What property_value_history does on Livedatalink
AI agents call property_value_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 |
|---|---|---|---|
county | string | — | County name (default: montgomery) |
account_number | string | Yes | County appraisal district account number |
Parameters from the server's own tool schema.
Why property_value_history is rated Low
This tool retrieves historical property valuation and tax assessment data without creating, modifying, deleting, or executing any operations. It answers analytical questions about property appreciation trends. The dependency on property_lookup for account numbers and the read-only nature of querying historical values confirm this is a data retrieval operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description explicitly states it 'Get[s] property value history and tax assessment trends' and 'Shows year-by-year market value' — pure data retrieval with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs property_value_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 property_value_history, this is the rule to start with:
property_value_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 property_value_history call is checked against it from then on.
Questions about property_value_history
Get property value history and tax assessment trends over multiple years. Shows year-by-year market value, land value, improvement value, and percentage change. Use this for questions like "how has this property's value changed?", "what's the appreciation rate?", "show me the tax assessment history", "has this home gone up in value?", or any property valuation trend question. Requires account number (use property_lookup first to find it). It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
property_value_history accepts 2 parameters: county, account_number. Required: account_number. 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 property_value_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.
property_value_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 property_value_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 property_value_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.
property_value_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