Search Arc Chromium history snapshots across local profiles.
AI agents call arc_search_history to retrieve information from Arc Browser MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves browsing history data from the Arc browser without modifying, deleting, or executing any operations. It is a pure query/search operation that fits the 'Read' category.
From the tool's definition Tool name is 'arc_search_history' and description states it 'Search[es] Arc Chromium history snapshots across local profiles.' The verb 'search' and the focus on querying historical data indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Search Arc Chromium history snapshots across local profiles. It is categorised as a Read tool in the Arc Browser MCP MCP Server, which means it retrieves data without modifying state.
Register the Arc Browser MCP server in PolicyLayer and add a rule for arc_search_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 Arc Browser MCP. Nothing to install.
arc_search_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 arc_search_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 arc_search_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.
arc_search_history is provided by the Arc Browser MCP server (jasoncronje/arc-browser-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 →