Get browser browsing history with top domains visited. Requires the ActivityWatch browser extension to be installed.
AI agents call get_browser_history to retrieve information from ActivityWatch 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 historical data about browsing activity without modifying, deleting, or executing anything. While the data sensitivity (browsing history) is noteworthy for privacy, the classification framework is based on technical operation type, not data sensitivity.
From the tool's definition Tool name 'get_browser_history' and description 'Get browser browsing history with top domains visited' indicate data retrieval. The verb 'Get' and the absence of any modification, deletion, or execution language confirm this is a read-only operation.
Attacks that exploit this kind of access
Get browser browsing history with top domains visited. Requires the ActivityWatch browser extension to be installed. It is categorised as a Read tool in the ActivityWatch MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ActivityWatch MCP Server MCP server in PolicyLayer and add a rule for get_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 ActivityWatch MCP Server. Nothing to install.
get_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 get_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 get_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.
get_browser_history is provided by the ActivityWatch MCP Server MCP server (jm-404/activitywatch-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →