take_screenshot

Take a screenshot of the page or element.

SERVERChrome DevTools MCP SOURCEanirbandz/chrome_mcp_devtool

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/anirbandz-chrome-mcp-devtool/take-screenshot.md

WHAT IT DOES

What take_screenshot does on Chrome DevTools MCP

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

RISK

Why take_screenshot is rated Low

Taking a screenshot is a read-only operation that queries the current state of a rendered page or DOM element. It retrieves visual information without creating, modifying, deleting, or executing arbitrary code. While screenshots could theoretically capture sensitive information (e.g., displayed credentials), the tool itself performs no destructive, financial, or code-execution actions.

From the tool's definition Tool name 'take_screenshot' and description 'Take a screenshot of the page or element' indicate a retrieval operation that captures visual state without modifying any data or triggering side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs take_screenshot safely

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

take_screenshot Allowed

take_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": {
    "take_screenshot": {}
  }
}

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

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

FAQ

Questions about take_screenshot

What does the take_screenshot tool do? +

Take a screenshot of the page or element. It is categorised as a Read tool in the Chrome DevTools MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on take_screenshot? +

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 MCP. Nothing to install.

What risk level is take_screenshot? +

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

Can I rate-limit take_screenshot? +

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.

How do I block take_screenshot completely? +

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.

What MCP server provides take_screenshot? +

take_screenshot is provided by the Chrome DevTools MCP server (anirbandz/chrome_mcp_devtool). 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 26 Chrome DevTools tools →

Across the catalogue

browser_screenshot on Percepta MCP Server → The MCP Attack Database →

Guides

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