screenshot

Takes a screenshot

SERVERChrome Devtools SOURCE@async23/chrome-devtools-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/async23-chrome-devtools-mcp/screenshot.md

WHAT IT DOES

What screenshot does on Chrome Devtools

AI agents call screenshot to retrieve information from Chrome Devtools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why screenshot is rated Low

Taking a screenshot is a non-destructive read operation. It captures the current visual state of a web page for inspection and analysis purposes. While the Chrome DevTools MCP server enables browser automation and control, the screenshot tool specifically performs observation only. It has no side effects, does not execute code, does not modify data, and does not trigger external operations.

From the tool's definition Tool name 'screenshot' with description 'Takes a screenshot' - a passive capture operation that retrieves visual state without modifying browser state, data, or external systems.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs screenshot safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Devtools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For screenshot, this is the rule to start with:

screenshot Allowed

screenshot is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "screenshot": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every screenshot call is checked against it from then on.

FAQ

Questions about screenshot

What does the screenshot tool do? +

Takes a screenshot. It is categorised as a Read tool in the Chrome Devtools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on screenshot? +

Register the Chrome Devtools MCP server in PolicyLayer and add a rule for 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.

What risk level is screenshot? +

screenshot is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit screenshot? +

Yes. Add a rate_limit block to the 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.

How do I block screenshot completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides screenshot? +

screenshot is provided by the Chrome Devtools MCP server (@async23/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Chrome Devtools, and thousands of servers like it.

This server

All 50 Chrome Devtools tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →