Low Risk

search_google_hotels_property

查询Google酒店详细信息

How to control search_google_hotels_property ↓

AI agents call search_google_hotels_property to retrieve information from searchAPI-mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves hotel information from Google Hotels - a read-only query operation with no side effects. Users can only view property details; they cannot book, modify, delete, or execute actions. The blast radius of misuse is minimal - an agent could only retrieve excess hotel data, not cause financial or operational harm.

From the tool's definition Tool name and description indicate querying hotel property details: 'search_google_hotels_property' with description '查询Google酒店详细信息' (query Google hotels detailed information).

Documented attack patterns abuse exactly the kind of access search_google_hotels_property gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and searchAPI-mcp, and nothing reaches the server without passing your rules. This is the rule we recommend for search_google_hotels_property:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_google_hotels_property": {}
  }
}

search_google_hotels_property is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register searchAPI-mcp — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the search_google_hotels_property tool do? +

查询Google酒店详细信息. It is categorised as a Read tool in the searchAPI-mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_google_hotels_property? +

Register the searchAPI- MCP server in PolicyLayer and add a rule for search_google_hotels_property: 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 searchAPI-mcp. Nothing to install.

What risk level is search_google_hotels_property? +

search_google_hotels_property is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_google_hotels_property? +

Yes. Add a rate_limit block to the search_google_hotels_property 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.

How do I block search_google_hotels_property completely? +

Set action: deny in the PolicyLayer policy for search_google_hotels_property. 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.

What MCP server provides search_google_hotels_property? +

search_google_hotels_property is provided by the searchAPI- MCP server (rmmargt/searchapi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every searchAPI-mcp tool call.

Deterministic rules across all 15 searchAPI-mcp tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

15 searchAPI-mcp tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.