Low Risk

google_search

Advanced Google Search with Cloudflare bypass, rich snippets detection, and multi-engine fallback

Accepts freeform code/query input (query); High parameter count (13 properties)

Part of the Rivalsearch MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call google_search to retrieve information from Rivalsearch without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though google_search only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

rashforddamion-rivalsearch.yaml
tools:
  google_search:
    rules:
      - action: allow

See the full Rivalsearch policy for all 18 tools.

Tool Name google_search
Category Read
Risk Level Low

View all 18 tools →

Agents calling read-class tools like google_search have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the google_search tool do? +

Advanced Google Search with Cloudflare bypass, rich snippets detection, and multi-engine fallback. It is categorised as a Read tool in the Rivalsearch MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on google_search? +

Add a rule in your Intercept YAML policy under the tools section for google_search. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Rivalsearch MCP server.

What risk level is google_search? +

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

Can I rate-limit google_search? +

Yes. Add a rate_limit block to the google_search rule in your Intercept 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 google_search completely? +

Set action: deny in the Intercept policy for google_search. 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 google_search? +

google_search is provided by the Rivalsearch MCP server (rashforddamion/rivalsearch). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Rivalsearch

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.