AI agents call search_google 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 retrieves and returns search results from Google. It performs no writes, deletions, code execution, or financial operations. The capability is limited to querying and presenting information, which is characteristic of a Read operation.
From the tool's definition Tool description states it 'searches Google search results, including organic results, knowledge graph, answer box, related questions, ads etc.' — this is a query/retrieval operation with no modification capability.
Documented attack patterns abuse exactly the kind of access search_google 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:
{
"version": "1",
"default": "deny",
"tools": {
"search_google": {}
}
}search_google 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: 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 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 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. 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 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.