Capture a full-page or viewport screenshot.
AI agents call browser_screenshot to retrieve information from DevLab MCP Suite without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Screenshots are passive observations of visual content and do not modify, delete, execute commands, or trigger external operations. Even in the context of a testing/automation suite, capturing a screenshot is fundamentally a Read operation. The low severity reflects minimal blast radius—an AI agent misusing this tool would only capture unintended visual information, not cause system harm or data loss.
From the tool's definition Tool performs screenshot capture, which is a data retrieval operation with no side effects. The description 'Capture a full-page or viewport screenshot' indicates read-only observation of visual state.
Attacks that exploit this kind of access
Capture a full-page or viewport screenshot. It is categorised as a Read tool in the DevLab MCP Suite MCP Server, which means it retrieves data without modifying state.
Register the DevLab MCP Suite 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 DevLab MCP Suite. 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 DevLab MCP Suite MCP server (tanguito86/devlab-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 →