Takes a screenshot of the current page. Use this tool to learn where you are on the page when controlling the browser with Stagehand. Only use this tool when the other tools are not sufficient to get the information you need.
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.
This tool retrieves visual information about the current state of a web page without modifying, executing commands, or triggering actions. It is a read-only observation capability analogous to a GET request or query. The capability to take screenshots could theoretically be misused for espionage or reconnaissance, but within the context of an LLM agent controlling a browser session it initiated, the risk is low.
From the tool's definition Tool description states it 'Takes a screenshot of the current page' and is used 'to learn where you are on the page' — a pure observation action with no side effects or state modifications.
Attacks that exploit this kind of access
Takes a screenshot of the current page. Use this tool to learn where you are on the page when controlling the browser with Stagehand. Only use this tool when the other tools are not sufficient to get the information you need. 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 (xxx00xxx33/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 →