Take a screenshot of the current browser page. Returns a base64-encoded PNG image.
AI agents call browser_screenshot to retrieve information from Mcp Browser without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Screenshots capture the current visual state of a webpage without modifying, executing code, deleting data, or triggering financial operations. This is a pure information retrieval action. While the parent server offers Execute capabilities (browser_evaluate, browser_click), this specific tool is confined to passive observation.
From the tool's definition Tool name 'browser_screenshot' and description 'Take a screenshot of the current browser page. Returns a base64-encoded PNG image.' indicate a read-only retrieval operation with no side effects.
Attacks that exploit this kind of access
Take a screenshot of the current browser page. Returns a base64-encoded PNG image. It is categorised as a Read tool in the Mcp Browser MCP Server, which means it retrieves data without modifying state.
Register the Mcp Browser 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 Mcp Browser. 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 Mcp Browser MCP server (mehranakila56-ops/mcp-browser-server). 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 →