property_lookup
Look up real estate property data by street address or account number. Returns assessed value, market value, land value, improvement value, year built, square footage, lot size, acreage, exemptions (homestead, over 65, disabled veteran), and legal description. Use this for questions like "how muc...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/property-lookup.md
What property_lookup does on Livedatalink
AI agents call property_lookup 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 |
|---|---|---|---|
query | string | Yes | Street address or appraisal district account number |
county | string | — | County name (default: montgomery) |
Parameters from the server's own tool schema.
Why property_lookup is rated Low
Even though property_lookup only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs property_lookup 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_lookup, this is the rule to start with:
property_lookup 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_lookup call is checked against it from then on.
Questions about property_lookup
Look up real estate property data by street address or account number. Returns assessed value, market value, land value, improvement value, year built, square footage, lot size, acreage, exemptions (homestead, over 65, disabled veteran), and legal description. Use this for questions like "how much is this property worth?", "what's the tax value of this address?", "what are the property details?", or any real estate lookup. Owner names, heirs, deed opinions, and title conclusions are not returned. Coverage note: currently demo dataset for Montgomery County, TX (sample properties only). Broader live county coverage is not enabled by default and must be confirmed before purchase. Email support@livedatalink.ai to discuss a source-verified coverage requirement. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
property_lookup accepts 2 parameters: query, county. Required: query. 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_lookup: 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_lookup 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_lookup 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_lookup. 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_lookup 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