AI agents call take_screenshot to retrieve information from PageMap 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 passive observation action with no side effects. It retrieves visual information about the current page state but does not create, modify, delete, or execute any operations. This clearly falls under the Read category, with low severity since it only exposes what is already visible on screen and poses minimal risk of misuse by an AI agent.
From the tool's definition Tool name is 'take_screenshot' and description states 'Take a screenshot of the current page.' This is a data retrieval operation that captures the visual state of a web page without modifying, deleting, or executing commands on that page.
Attacks that exploit this kind of access
Take a screenshot of the current page. It is categorised as a Read tool in the PageMap MCP Server, which means it retrieves data without modifying state.
Register the PageMap MCP server in PolicyLayer and add a rule for take_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 PageMap. Nothing to install.
take_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 take_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 take_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.
take_screenshot is provided by the PageMap MCP server (oci:docker.io/retio1001/pagemap:0.7.3). 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 →