AI agents call capture_screenshot to retrieve information from Chrome Tools MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Capturing a screenshot retrieves visual state of a web page without modifying, executing, or destroying any data. The action is non-destructive and produces only a read-only artifact.
From the tool's definition Tool name 'capture_screenshot' indicates retrieval of visual data from a Chrome tab with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access capture_screenshot gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Chrome Tools MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for capture_screenshot:
{
"version": "1",
"default": "deny",
"tools": {
"capture_screenshot": {}
}
}capture_screenshot is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
capture_screenshot. It is categorised as a Read tool in the Chrome Tools MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Chrome Tools MCP Server MCP server in PolicyLayer and add a rule for capture_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 Tools MCP Server. Nothing to install.
capture_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 capture_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 capture_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.
capture_screenshot is provided by the Chrome Tools MCP Server MCP server (nicholmikey/chrome-tools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Chrome Tools MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 Chrome Tools MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.