// SCAN REPORT

Web Search MCP

4 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 12 Jun 2026

1 can modify or destroy data

3 read-only

4 tools total

Community server · catalogue entry verified 12/06/2026

How to control Web Search MCP ↓

TOOL MAP

What Web Search MCP exposes to your agents

Read (3) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Web Search MCP tools

Write · Medium reset_search_engines This tool modifies the state of the application by clearing/resetting the blocked search engines list.

1 of Web Search MCP's 4 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Web Search MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and Web Search MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "reset_search_engines": {
    "limits": [
      {
        "counter": "reset_search_engines_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_search_engine_status": {
    "limits": [
      {
        "counter": "get_search_engine_status_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Web Search MCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON WEB SEARCH →

Free to start. No card required.

FULL CATALOGUE

All 4 Web Search MCP tools

WRITE 1 tools

Write reset_search_engines Reset the blocked search engines list (useful if engines recover from blocks).

READ 3 tools

Read get_search_engine_status Get the current status of all search engines (available/blocked) and the active browser backend. Read get_webpage_content Fetch and return the text content of a webpage. Read search_web search_web

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Web Search MCP

How do I prevent bulk modifications through Web Search MCP? +

The Web Search MCP server has 1 write tools including reset_search_engines. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Web Search MCP.

How many tools does the Web Search MCP server expose? +

4 tools across 2 categories: Destructive, Read. 3 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Web Search MCP? +

Register the Web Search MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Web Search MCP tool call.

Deterministic rules across all 4 Web Search MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON WEB SEARCH →

Free to start. No card required.

4 Web Search MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.