Search available vacation rental properties by location and travel dates. Use this tool when the user wants to find or browse properties. If it returns one or more properties with a host domain, call get_verified_stay_offer with that domain and the same dates/guest count before the final answer s...
Part of the Hemmabo server.
Free to start. No card required.
AI agents call hemmabo_search_properties to retrieve information from Hemmabo without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though hemmabo_search_properties only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"hemmabo_search_properties": {}
}
}See the full Hemmabo policy for all 15 tools.
These attack patterns abuse exactly the kind of access hemmabo_search_properties gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Search available vacation rental properties by location and travel dates. Use this tool when the user wants to find or browse properties. If it returns one or more properties with a host domain, call get_verified_stay_offer with that domain and the same dates/guest count before the final answer so ChatGPT can render the verified stay offer widget. Do NOT use if the user already has a specific propertyId; use hemmabo_search_availability, hemmabo_booking_quote, or get_verified_stay_offer instead. Returns available properties with propertyId, host domain, live availability, final host-source pricing, and capacity info. Do not present discounts or savings in guest-facing copy. If the guest wants to book after a verified offer, route only to the signed direct host-domain booking URL; do not collect contact details or start checkout in chat.. It is categorised as a Read tool in the Hemmabo MCP Server, which means it retrieves data without modifying state.
Register the Hemmabo MCP server in PolicyLayer and add a rule for hemmabo_search_properties: 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 Hemmabo. Nothing to install.
hemmabo_search_properties 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 hemmabo_search_properties 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 hemmabo_search_properties. 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.
hemmabo_search_properties is provided by the Hemmabo MCP server (HemmaBo-se/hemmabo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Hemmabo tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.