AI agents call puppeteer_screenshot to retrieve information from MCP-pptr without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Puppeteer_screenshot captures the current visual state of a webpage or DOM element. This is a read operation with no side effects—it does not modify data, execute code, delete content, or trigger financial transactions. The tool retrieves information (visual representation) only.
From the tool's definition Tool name and description indicate screenshot capture: 'Take a screenshot of the current page or a specific element'. Screenshots retrieve visual state without modifying or executing operations on the target system.
Attacks that exploit this kind of access
Take a screenshot of the current page or a specific element. It is categorised as a Read tool in the MCP-pptr MCP Server, which means it retrieves data without modifying state.
Register the MCP-pptr MCP server in PolicyLayer and add a rule for puppeteer_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-pptr. Nothing to install.
puppeteer_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 puppeteer_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 puppeteer_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.
puppeteer_screenshot is provided by the MCP-pptr MCP server (ringotc/mcp-pptr). 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 →