Capture a screenshot of the current page. Restrictions: Can capture either the full page or the visible viewport. Valid: Take a screenshot of the current browser view. Invalid: Capture a screenshot of a specific element (not supported).
AI agents call browser_screenshot to retrieve information from Scrapeless Ai Scrapeless 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 purely observational action that reads the current visual state of a web page. It has no side effects, does not modify data, does not execute code or commands, does not delete anything, and does not involve financial operations. This is a typical Read category tool used for information gathering only.
From the tool's definition The tool captures a screenshot of the current page, which is a retrieval operation that retrieves visual data without modifying any state. The description explicitly states it 'captures' a screenshot and lists no data modification capabilities.
Attacks that exploit this kind of access
Capture a screenshot of the current page. Restrictions: Can capture either the full page or the visible viewport. Valid: Take a screenshot of the current browser view. Invalid: Capture a screenshot of a specific element (not supported). It is categorised as a Read tool in the Scrapeless Ai Scrapeless MCP Server, which means it retrieves data without modifying state.
Register the Scrapeless Ai Scrapeless 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 Scrapeless Ai Scrapeless. 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 Scrapeless Ai Scrapeless MCP server (@iflow-mcp/scrapeless-ai-scrapeless-mcp-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 →