Low Risk

search_google_hotels_property

获取Google酒店详细信息

How to control search_google_hotels_property ↓

What search_google_hotels_property does on SearchAPI MCP Agent

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

Low Risk

Why search_google_hotels_property needs a policy

This tool queries and retrieves hotel property details from Google Hotels. It is a read-only operation that fetches information without modifying any data, executing code, or causing side effects. The retrieval of publicly-available hotel information poses minimal security risk even if misused by an AI agent.

From the tool's definition Tool name 'search_google_hotels_property' and description 'retrieves Google hotel detailed information' indicate a data retrieval operation with no mutation, creation, deletion, or execution of external code.

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

How to control search_google_hotels_property

PolicyLayer is an MCP gateway — it sits between your AI agents and SearchAPI MCP Agent, 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 Agent — 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.

Related tools and policies

Go deeper

Questions about search_google_hotels_property

What does the search_google_hotels_property tool do? +

获取Google酒店详细信息. It is categorised as a Read tool in the SearchAPI MCP Agent 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 Agent 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 Agent. 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 Agent MCP server (rmmargt/searchapi-mcp-agent). 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 Agent tool call.

Start from SearchAPI MCP Agent, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

9 SearchAPI MCP Agent tools catalogued and risk-classified — across an index of 43,000+ 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.