Capture element images from the runner
AI agents call capture_gui_elements to retrieve information from Qontinui MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/captures visual information (element images) from the Qontinui Runner for inspection or analysis purposes. It is a Read operation with no destructive, financial, or code-execution implications. Blast radius is minimal as the tool only observes existing GUI state without triggering automation or altering system state.
From the tool's definition Tool name and description indicate data retrieval only: 'Capture element images' implies querying or extracting visual state from the runner without modifying or executing operations. No side effects or state changes are described.
Attacks that exploit this kind of access
Capture element images from the runner. It is categorised as a Read tool in the Qontinui MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Qontinui MCP Server MCP server in PolicyLayer and add a rule for capture_gui_elements: 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 Qontinui MCP Server. Nothing to install.
capture_gui_elements 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 capture_gui_elements 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 capture_gui_elements. 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.
capture_gui_elements is provided by the Qontinui MCP Server MCP server (qontinui/qontinui-mcp). 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 →