AI agents call get_most_visited to retrieve information from Search History MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves browsing statistics (most visited sites) from browser history—a read-only operation with no side effects. While browser history may contain sensitive information, the tool itself only queries existing data and cannot modify, delete, or execute actions. Severity is low because exposure is limited to reading user behavior data without operational impact.
From the tool's definition Tool name 'get_most_visited' and server description indicating 'access to and searching of browser history' and 'retrieve past browsing data' confirm this retrieves historical data with no modification capability.
Documented attack patterns abuse exactly the kind of access get_most_visited gives an agent:
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. This is the rule we recommend for get_most_visited:
{
"version": "1",
"default": "deny",
"tools": {
"get_most_visited": {}
}
}get_most_visited 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.
get_most_visited. It is categorised as a Read tool in the Search History MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Search History MCP Server MCP server in PolicyLayer and add a rule for get_most_visited: 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 Search History MCP Server. Nothing to install.
get_most_visited 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 get_most_visited 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 get_most_visited. 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.
get_most_visited is provided by the Search History MCP Server MCP server (ronantakizawa/search-history-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Search History MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Search History MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.