AI agents call scroll_to_element_and_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 only scrolls to an element and captures a screenshot — both are read-only, non-destructive actions that retrieve visual data without modifying any state.
From the tool's definition Scroll to a specific element and take a screenshot of it
Attacks that exploit this kind of access
Scroll to a specific element and take a screenshot of it. 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 scroll_to_element_and_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.
scroll_to_element_and_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 scroll_to_element_and_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 scroll_to_element_and_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.
scroll_to_element_and_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 →