Capture a full-page screenshot and return it (and save as a resource).
AI agents call browserbase_screenshot to retrieve information from Browserbase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Taking a screenshot is a passive observation mechanism that retrieves visual information without side effects. It does not create, modify, delete, or execute operations on the website being screened. The severity is low because screenshots alone cannot directly compromise systems, though they may reveal sensitive information if the target page contains it.
From the tool's definition Tool captures and returns a screenshot with no modification of the underlying website or data. Description explicitly states 'Capture a full-page screenshot and return it' with no mention of data modification, deletion, or execution of commands on the target…
Attacks that exploit this kind of access
Capture a full-page screenshot and return it (and save as a resource). It is categorised as a Read tool in the Browserbase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Browserbase MCP Server MCP server in PolicyLayer and add a rule for browserbase_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 Browserbase MCP Server. Nothing to install.
browserbase_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 browserbase_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 browserbase_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.
browserbase_screenshot is provided by the Browserbase MCP Server MCP server (mesuterpikin/mcp-server-browserbase). 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 →