// SCAN REPORT

Search History MCP Server

3 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 12 Jun 2026

0 can modify or destroy data

3 read-only

3 tools total

Community server · catalogue entry verified 12/06/2026

How to control Search History MCP Server ↓

TOOL MAP

What Search History MCP Server exposes to your agents

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

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control Search History MCP Server

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

Cap read operations

{
  "get_most_visited": {
    "limits": [
      {
        "counter": "get_most_visited_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 Search History MCP Server — 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 SEARCH HISTORY →

Free to start. No card required.

FULL CATALOGUE

All 3 Search History MCP Server tools

READ 3 tools

Read get_most_visited get_most_visited Read get_recent_history get_recent_history Read search_history search_history

FAQ

Questions about Search History MCP Server

Is the Search History MCP Server MCP server safe to use without restrictions? +

The Search History MCP Server server is primarily read-only with 3 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Search History MCP Server MCP server expose? +

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

How do I enforce a policy on Search History MCP Server? +

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

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

ENFORCE POLICY ON SEARCH HISTORY →

Free to start. No card required.

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