AI agents call search_google_hotels 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.
This tool retrieves and queries hotel information from Google Hotels. It is a read-only operation with no side effects, no data modification, no code execution, and no financial transactions. The blast radius of misuse is minimal—an AI agent cannot cause harm by searching hotels repeatedly or retrieving irrelevant results.
From the tool's definition Tool name 'search_google_hotels' and description '搜索Google酒店信息' (search Google hotel information) indicate a search/query operation that retrieves hotel data without modifying or executing operations.
Documented attack patterns abuse exactly the kind of access search_google_hotels 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:
{
"version": "1",
"default": "deny",
"tools": {
"search_google_hotels": {}
}
}search_google_hotels is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
搜索Google酒店信息. It is categorised as a Read tool in the searchAPI-mcp MCP Server, which means it retrieves data without modifying state.
Register the searchAPI- MCP server in PolicyLayer and add a rule for search_google_hotels: 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.
search_google_hotels 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 search_google_hotels 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 search_google_hotels. 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.
search_google_hotels 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.
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.