AI agents call analyze_browser_history to retrieve information from Browser History Analysis MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs analysis on existing browser history data without modifying, deleting, or executing external operations. Analysis of local browser history—even identifying patterns—is a retrieval/query operation with no side effects. Low severity because the blast radius of misuse is limited to reading user browsing patterns from local data.
From the tool's definition Tool name is 'analyze_browser_history' and server description states it 'retrieves and analyzing your browser history' and 'identify patterns, analyze sessions, and create a comprehensive report.' Sibling tools include 'get_browser_history' and…
Documented attack patterns abuse exactly the kind of access analyze_browser_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Browser History Analysis MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_browser_history:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_browser_history": {}
}
}analyze_browser_history 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.
analyze_browser_history. It is categorised as a Read tool in the Browser History Analysis MCP MCP Server, which means it retrieves data without modifying state.
Register the Browser History Analysis MCP server in PolicyLayer and add a rule for analyze_browser_history: 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 Browser History Analysis MCP. Nothing to install.
analyze_browser_history 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 analyze_browser_history 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 analyze_browser_history. 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.
analyze_browser_history is provided by the Browser History Analysis MCP server (mixophrygian/browser_history_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Browser History Analysis MCP, 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.
7 Browser History Analysis MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.