Take a screenshot of the current page. Returns base64-encoded PNG.
AI agents call screenshot to retrieve information from WebControl without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Taking a screenshot captures visual information for inspection purposes only. It does not create, modify, delete, execute code, move money, or trigger external operations. This is a pure Read operation with minimal risk—the worst case is information disclosure of what is currently visible on the page, which has already been navigated to by the agent.
From the tool's definition The tool 'Take a screenshot of the current page. Returns base64-encoded PNG.' retrieves visual data from the current browser state without modifying anything. Screenshots are read-only operations with no side effects.
Attacks that exploit this kind of access
Take a screenshot of the current page. Returns base64-encoded PNG. It is categorised as a Read tool in the WebControl MCP Server, which means it retrieves data without modifying state.
Register the WebControl 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 WebControl. 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 WebControl MCP server (matansht/webcontrol). 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 →