browser_action_history
A read tool on the Looking Glass MCP server.
This record as markdown: /tools/io-github-sahib-sawhney-wh-looking-glass-mcp/browser-action-history.md
What browser_action_history does on Looking Glass
AI agents call browser_action_history to retrieve information from Looking Glass without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
last | number | — | Return only the last N entries (default: all) |
Parameters from the server's own tool schema.
Why browser_action_history is rated Low
The tool name indicates it retrieves or queries browser action history—a read-only operation with no side effects. The empty description lowers confidence slightly, but the naming convention (browser_*_history) and context of sibling tools (which are predominantly inspection/diagnostic in nature) strongly suggest this is a data retrieval tool. No evidence of write, execute, destructive, or financial capabilities.
From the tool's definition Tool name 'browser_action_history' suggests retrieval of historical browser actions; no description provided, but naming pattern indicates query/retrieval functionality consistent with sibling tools like 'browser_console_messages' and 'browser_diagnose'.
Attacks that exploit this kind of access
The rule that runs browser_action_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Looking Glass, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_action_history, this is the rule to start with:
browser_action_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Looking Glass, apply this rule, and every browser_action_history call is checked against it from then on.
Questions about browser_action_history
browser_action_history is a read tool on the Looking Glass MCP server. It is categorised as a Read tool in the Looking Glass MCP Server, which means it retrieves data without modifying state.
browser_action_history accepts 1 parameter: last. The full parameter table on this page comes from the server's own tool schema.
Register the Looking Glass MCP server in PolicyLayer and add a rule for browser_action_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 Looking Glass. Nothing to install.
browser_action_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 browser_action_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 browser_action_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.
browser_action_history is provided by the Looking Glass MCP server (looking-glass-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Looking Glass, and thousands of servers like it.
This server
Across the catalogue