Take a screenshot of the current page (Note: May fail on some configurations due to stack overflow issues. Consider using get_content for content analysis instead)
AI agents call screenshot to retrieve information from Puppeteer Real Browser without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A screenshot operation only reads the current visual state of the browser page and returns an image. It does not modify, delete, or execute anything. The description even suggests using get_content as an alternative for content analysis, reinforcing the read-only nature. Severity is low as the worst misuse would be capturing sensitive on-screen information, but it causes no direct system changes.
From the tool's definition 'Take a screenshot of the current page' — purely captures visual state, no side effects
Attacks that exploit this kind of access
Take a screenshot of the current page (Note: May fail on some configurations due to stack overflow issues. Consider using get_content for content analysis instead). It is categorised as a Read tool in the Puppeteer Real Browser MCP Server, which means it retrieves data without modifying state.
Register the Puppeteer Real Browser MCP server in PolicyLayer and add a rule for 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 Puppeteer Real Browser. Nothing to install.
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 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 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.
screenshot is provided by the Puppeteer Real Browser MCP server (puppeteer-real-browser-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 →