property_search_owner
Filter the bounded Montgomery County, TX demo property records by a supplied owner-name query. Partial matching is supported, but owner names are not returned. Matching results include addresses, values, property types, and account numbers for the sample records. This is not an owner-verification...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/property-search-owner.md
What property_search_owner does on Livedatalink
AI agents call property_search_owner 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) |
owner_name | string | Yes | Full or partial owner name to search for |
Parameters from the server's own tool schema.
Why property_search_owner is rated Low
Even though property_search_owner 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_search_owner 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_search_owner, this is the rule to start with:
property_search_owner 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_search_owner call is checked against it from then on.
Questions about property_search_owner
Filter the bounded Montgomery County, TX demo property records by a supplied owner-name query. Partial matching is supported, but owner names are not returned. Matching results include addresses, values, property types, and account numbers for the sample records. This is not an owner-verification or people-finder service. Coverage note: the current Montgomery County, TX connector returns demo/sample records only. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
property_search_owner accepts 2 parameters: county, owner_name. Required: owner_name. 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_search_owner: 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_search_owner 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_search_owner 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_search_owner. 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_search_owner 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