browser_screenshot
A read tool on the Looking Glass MCP server.
This record as markdown: /tools/io-github-sahib-sawhney-wh-looking-glass-mcp/browser-screenshot.md
What browser_screenshot does on Looking Glass
AI agents call browser_screenshot 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 |
|---|---|---|---|
fullPage | boolean | — | Capture full page (default: viewport only) |
savePath | string | — | Custom save path (default: auto-generated in sessions dir) |
selector | string | — | CSS selector to screenshot specific element |
Parameters from the server's own tool schema.
Why browser_screenshot is rated Low
Taking a screenshot retrieves visual information from the browser without modifying, deleting, or executing code. The tool captures data for inspection. While the description is empty (lowering confidence slightly), the name clearly indicates a passive observation action typical of browser automation testing/analysis tools.
From the tool's definition Tool name is 'browser_screenshot' which captures visual state of a webpage. No description provided, but screenshot operations are read-only and non-destructive.
Attacks that exploit this kind of access
The rule that runs browser_screenshot 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_screenshot, this is the rule to start with:
browser_screenshot 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_screenshot call is checked against it from then on.
Questions about browser_screenshot
browser_screenshot 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_screenshot accepts 3 parameters: fullPage, savePath, selector. 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_screenshot: 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_screenshot 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_screenshot 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_screenshot. 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_screenshot 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