chrome_take_screenshot

Take a screenshot of the current page

SERVERChrome Feedback SOURCE2019-02-18/mcx

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/2019-02-18-mcx/chrome-take-screenshot.md

WHAT IT DOES

What chrome_take_screenshot does on Chrome Feedback

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

RISK

Why chrome_take_screenshot is rated Low

Taking a screenshot is a read-only operation that retrieves visual information from the current page state. It does not create, modify, delete, or execute code. While screenshots could theoretically capture sensitive information visible on screen, the tool itself performs no destructive, financial, or execution-based actions.

From the tool's definition Tool name 'chrome_take_screenshot' and description 'Take a screenshot of the current page' indicate a data retrieval operation with no side effects—it captures visual content of the current state without modifying, deleting, or executing external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs chrome_take_screenshot safely

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

chrome_take_screenshot Allowed

chrome_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": {
    "chrome_take_screenshot": {}
  }
}

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

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

FAQ

Questions about chrome_take_screenshot

What does the chrome_take_screenshot tool do? +

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

How do I enforce a policy on chrome_take_screenshot? +

Register the Chrome Feedback MCP server in PolicyLayer and add a rule for chrome_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 Feedback. Nothing to install.

What risk level is chrome_take_screenshot? +

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

Can I rate-limit chrome_take_screenshot? +

Yes. Add a rate_limit block to the chrome_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 chrome_take_screenshot completely? +

Set action: deny in the PolicyLayer policy for chrome_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 chrome_take_screenshot? +

chrome_take_screenshot is provided by the Chrome Feedback MCP server (2019-02-18/mcx). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

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

This server

All 16 Chrome Feedback tools →

Across the catalogue

The MCP Attack Database →

Guides

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