Take a screenshot of the page or element.
AI agents call take_screenshot to retrieve information from Chrome Devtools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Screenshots retrieve visual data from a rendered page with no side effects, no data modification, no code execution, and no destructive operations. This is a read-only capability that gathers information about the current state of the browser. The low severity reflects minimal risk of misuse — screenshots cannot directly harm systems, though they could theoretically capture sensitive UI elements if present on screen.
From the tool's definition Tool description states 'Take a screenshot of the page or element' — a purely observational action that captures visual state without modifying anything or executing code.
Attacks that exploit this kind of access
Take a screenshot of the page or element. It is categorised as a Read tool in the Chrome Devtools MCP Server, which means it retrieves data without modifying state.
Register the Chrome Devtools MCP server in PolicyLayer and add a rule for take_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 Devtools. Nothing to install.
take_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 take_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 take_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.
take_screenshot is provided by the Chrome Devtools MCP server (zhang77-x/chrpme_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 →