hdb_resale_search
Retrieve official HDB resale rows using exact town, flat-type, month and street filters with deterministic sorting and pagination. For medians, quartiles, price ranges or latest-period aggregation, use hdb_resale_stats in the aggregate Singapore MCP.
This record as markdown: /tools/olano-mcp-singapore/hdb-resale-search.md
What hdb_resale_search does on Mcp Singapore
AI agents call hdb_resale_search to retrieve information from Mcp Singapore 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 |
|---|---|---|---|
town | string | — | |
block | string | — | |
limit | integer | — | |
month | string | — | |
query | string | — | Legacy data.gov.sg full-text query. Prefer the structured filters because multi-term q searches may be rejected upstream. |
offset | integer | — | |
street | string | — | |
flatType | string | — | |
flatModel | string | — | |
sortOrder | string | — |
Parameters from the server's own tool schema.
Why hdb_resale_search is rated Low
Even though hdb_resale_search 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.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs hdb_resale_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Singapore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hdb_resale_search, this is the rule to start with:
hdb_resale_search 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 Mcp Singapore, apply this rule, and every hdb_resale_search call is checked against it from then on.
Questions about hdb_resale_search
Retrieve official HDB resale rows using exact town, flat-type, month and street filters with deterministic sorting and pagination. For medians, quartiles, price ranges or latest-period aggregation, use hdb_resale_stats in the aggregate Singapore MCP. It is categorised as a Read tool in the Mcp Singapore MCP Server, which means it retrieves data without modifying state.
hdb_resale_search accepts 10 parameters: town, block, limit, month, query, offset, street, flatType, flatModel, sortOrder. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Singapore MCP server in PolicyLayer and add a rule for hdb_resale_search: 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 Mcp Singapore. Nothing to install.
hdb_resale_search 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 hdb_resale_search 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 hdb_resale_search. 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.
hdb_resale_search is provided by the Mcp Singapore MCP server (@olano/mcp-singapore). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Singapore, and thousands of servers like it.
This server
Across the catalogue