Advanced screenshot capture with element targeting, full-page support, and custom dimensions
AI agents call chrome_screenshot to retrieve information from Chrome MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool captures and retrieves visual snapshots of web pages or specific elements. It produces no side effects, creates no data modifications, executes no code, and does not delete anything. While screenshots could potentially expose sensitive information visible on screen, the tool itself is fundamentally a read operation.
From the tool's definition Tool name is 'chrome_screenshot' and description states it performs 'Advanced screenshot capture with element targeting, full-page support, and custom dimensions'.
Attacks that exploit this kind of access
Advanced screenshot capture with element targeting, full-page support, and custom dimensions. It is categorised as a Read tool in the Chrome MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Chrome MCP Server MCP server in PolicyLayer and add a rule for chrome_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 Chrome MCP Server. Nothing to install.
chrome_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 chrome_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 chrome_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.
chrome_screenshot is provided by the Chrome MCP Server MCP server (mnisred/mcp-chrome). 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 →