Take a screenshot of the active tab (returns base64 PNG). Args: tab_id: Optional tab ID to screenshot. Uses active tab if empty.
AI agents call browser_screenshot to retrieve information from Cdp Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Screenshots retrieve visual information from the current browser state with no side effects. The tool cannot modify data, execute arbitrary code, delete content, or move money. It falls squarely into the Read category with low severity, as misuse would only expose what is already visible on the user's screen.
From the tool's definition Tool name is 'browser_screenshot' and description states it 'Take[s] a screenshot of the active tab (returns base64 PNG)'.
Documented attack patterns abuse exactly the kind of access browser_screenshot gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cdp Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_screenshot:
{
"version": "1",
"default": "deny",
"tools": {
"browser_screenshot": {}
}
}browser_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.
Take a screenshot of the active tab (returns base64 PNG). Args: tab_id: Optional tab ID to screenshot. Uses active tab if empty. It is categorised as a Read tool in the Cdp Bridge MCP Server, which means it retrieves data without modifying state.
Register the Cdp Bridge MCP server in PolicyLayer and add a rule for browser_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 Cdp Bridge. Nothing to install.
browser_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 browser_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 browser_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.
browser_screenshot is provided by the Cdp Bridge MCP server (unagi-cq/cdp-bridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 Cdp Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
9 Cdp Bridge tools catalogued and risk-classified — across an index of 42,500+ MCP servers.