realestate.location.suggest
Autocomplete location search for US real estate — returns matching cities, ZIP codes, and addresses with coordinates. Use to find valid city/state codes for property searches (RapidAPI / Realtor.com data)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/realestate.location.suggest.md
What realestate.location.suggest does on Apibase
AI agents call realestate.location.suggest 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 |
|---|---|---|---|
query | string | Yes | Location search query — city name, address, or ZIP code (e.g. "Austin TX", "90210") |
Parameters from the server's own tool schema.
Why realestate.location.suggest is rated Low
Retrieves public real estate location data without side effects or modifications.
From the tool's definition Autocomplete location search returns matching cities, ZIP codes, addresses.
Attacks that exploit this kind of access
The rule that runs realestate.location.suggest 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.location.suggest, this is the rule to start with:
realestate.location.suggest 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.location.suggest call is checked against it from then on.
Questions about realestate.location.suggest
Autocomplete location search for US real estate — returns matching cities, ZIP codes, and addresses with coordinates. Use to find valid city/state codes for property searches (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.location.suggest accepts 1 parameter: query. Required: query. 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.location.suggest: 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.location.suggest 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.location.suggest 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.location.suggest. 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.location.suggest 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