AI agents call screenshot to retrieve information from InSite without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves visual content from the current browser page state. It has no side effects, does not modify data, execute arbitrary commands, or delete anything. It is a straightforward read operation analogous to fetching or querying page content. The low severity reflects minimal harm potential even if misused by an agent—screenshots cannot damage systems or data.
From the tool's definition Tool description: 'Take a screenshot of the current page' — a passive operation that captures visual state without modifying, deleting, or executing code.
Attacks that exploit this kind of access
Take a screenshot of the current page. It is categorised as a Read tool in the InSite MCP Server, which means it retrieves data without modifying state.
Register the InSite 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 InSite. 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 InSite MCP server (jowharshamshiri/insite). 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 →