Take a screenshot of the current page. Returns base64-encoded image data.
AI agents call browserbeam_screenshot to retrieve information from Browserbeam 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 action that retrieves visual information without side effects or capability to alter the web page, execute code, or trigger external operations. It falls squarely into the Read category (retrieves data with no side effects).
From the tool's definition Tool takes a screenshot and returns base64-encoded image data. No modification, deletion, or execution of code occurs. The description explicitly states it retrieves visual data from the current page state.
Attacks that exploit this kind of access
Take a screenshot of the current page. Returns base64-encoded image data. It is categorised as a Read tool in the Browserbeam MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Browserbeam MCP Server MCP server in PolicyLayer and add a rule for browserbeam_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 Browserbeam MCP Server. Nothing to install.
browserbeam_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 browserbeam_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 browserbeam_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.
browserbeam_screenshot is provided by the Browserbeam MCP Server MCP server (nyku/browserbeam-mcp). 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 →