Save page screenshot to file or return as base64. Supports full-page capture, region clipping, and multiple image formats.\n\nWhen to use: Capturing a screenshot for saving to disk or when the full-page or clipped region is needed.\nWhen NOT to use: Use computer(action:
AI agents call page_screenshot to retrieve information from OpenChrome without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A screenshot tool captures the visual state of a webpage and either saves it to disk or returns it as base64-encoded data. This is purely a read operation—it retrieves information about the current page state without creating, modifying, deleting, or executing any logic on the page or backend systems. The captured image is a snapshot of existing content, making it analogous to a 'get' or 'fetch' operation.
From the tool's definition The tool 'Save page screenshot to file or return as base64' performs screenshot capture, which retrieves visual data from the current page without modifying state, executing code, or triggering external operations.
Documented attack patterns abuse exactly the kind of access page_screenshot gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenChrome, and nothing reaches the server without passing your rules. This is the rule we recommend for page_screenshot:
{
"version": "1",
"default": "deny",
"tools": {
"page_screenshot": {}
}
}page_screenshot 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.
Save page screenshot to file or return as base64. Supports full-page capture, region clipping, and multiple image formats.\n\nWhen to use: Capturing a screenshot for saving to disk or when the full-page or clipped region is needed.\nWhen NOT to use: Use computer(action:. It is categorised as a Read tool in the OpenChrome MCP Server, which means it retrieves data without modifying state.
Register the OpenChrome MCP server in PolicyLayer and add a rule for page_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 OpenChrome. Nothing to install.
page_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 page_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 page_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.
page_screenshot is provided by the OpenChrome MCP server (shaun0927/openchrome). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 106 OpenChrome tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
106 OpenChrome tools catalogued and risk-classified — across an index of 42,500+ MCP servers.