Capture a screenshot of a browser tab. Returns base64-encoded image.
AI agents call capture_screenshot to retrieve information from Chrome Extension MCP Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Capturing a screenshot queries visual state of the currently rendered page and returns the result without modifying, executing, or deleting anything. It is analogous to a GET request. The risk is low because screenshots do not alter system state, though they may reveal sensitive information if the page contains it—justifying 'low' rather than negligible severity.
From the tool's definition Tool description states it 'Capture[s] a screenshot' and 'Returns base64-encoded image'—a passive retrieval operation with no side effects on the browser state or data.
Attacks that exploit this kind of access
Capture a screenshot of a browser tab. Returns base64-encoded image. It is categorised as a Read tool in the Chrome Extension MCP Bridge MCP Server, which means it retrieves data without modifying state.
Register the Chrome Extension MCP Bridge 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 Extension MCP Bridge. 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 Extension MCP Bridge MCP server (ivoglent/chrome-mcp-bridge). 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 →