Search

36 tools. 21 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated:

21 can modify or destroy data
15 read-only
36 tools total

Community server · catalogue entry verified 12/06/2026

How to control Search ↓

What Search exposes to your agents

Read (15) Write / Execute (19) Destructive / Financial (1)
Critical Risk

The most dangerous Search tools

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

How to control Search

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

Deny destructive operations
{
  "browser_close_tab": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "create_directory": {
    "limits": [
      {
        "counter": "create_directory_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "browser_get_download_list": {
    "limits": [
      {
        "counter": "browser_get_download_list_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

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

Free to start. No card required.

All 36 Search tools

Related servers

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

Questions about Search

Can an AI agent delete data through the Search MCP server? +

Yes. The Search server exposes 1 destructive tools including browser_close_tab. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Search? +

The Search server has 4 write tools including create_directory, edit_file, move_file. 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 Search.

How many tools does the Search MCP server expose? +

36 tools across 3 categories: Execute, Read, Write. 15 are read-only. 21 can modify, create, or delete data.

How do I enforce a policy on Search? +

Register the 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 Search tool call.

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

Free to start. No card required.

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

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.