AI agents call element_screenshot_compare 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 and analyzes visual representations of page elements to compare them. Comparison is a read-only operation that does not create, modify, delete, or execute external commands. While it may capture screenshots (similar to sibling tools like 'capture_full_scrollable_page'), the comparison itself is a non-destructive analytical operation.
From the tool's definition Tool name 'element_screenshot_compare' and description 'Compare specific elements across different states or versions' indicate a comparison/analysis operation that captures and compares visual states without modifying underlying data or triggering external…
Attacks that exploit this kind of access
Compare specific elements across different states or versions. 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 element_screenshot_compare: 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.
element_screenshot_compare 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 element_screenshot_compare 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 element_screenshot_compare. 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.
element_screenshot_compare 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 →