AI agents call search_google_ai_mode 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.
The tool appears to be a Google search variant based on its name and sibling tools on this server, which are all Read-category search operations. Although the description is empty, the naming convention and context strongly suggest this performs a search query rather than modifying, executing, or deleting data. Confidence is lowered due to lack of explicit description clarifying the tool's exact function.
From the tool's definition Tool name 'search_google_ai_mode' contains 'search_google' prefix, consistent with sibling tools (search_google, search_google_events, search_google_flights, search_google_hotels, search_google_maps) that are all query/retrieval operations.
Documented attack patterns abuse exactly the kind of access search_google_ai_mode 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_ai_mode:
{
"version": "1",
"default": "deny",
"tools": {
"search_google_ai_mode": {}
}
}search_google_ai_mode 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.
search_google_ai_mode. 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_ai_mode: 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_ai_mode 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_ai_mode 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_ai_mode. 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_ai_mode 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.