Take a screenshot of the current page
AI agents call screenshot to retrieve information from QA Agent Pro without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Screenshot captures the current state of a webpage visually for inspection/testing purposes. It retrieves visual information without creating, modifying, deleting, or executing operations. This is a read-only action typical of automated testing. Risk is minimal since screenshots alone cannot harm systems or data. The tool is appropriately classified as Read with low severity.
From the tool's definition Tool name: 'screenshot'. Description: 'Take a screenshot of the current page'. The tool captures visual state of a page without modifying data, executing commands, or triggering side effects.
Attacks that exploit this kind of access
Take a screenshot of the current page. It is categorised as a Read tool in the QA Agent Pro MCP Server, which means it retrieves data without modifying state.
Register the QA Agent Pro 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 QA Agent Pro. 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 QA Agent Pro MCP server (samusilv/qa-agent-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 →