capture_window
Capture a screenshot of the frontmost window. Optionally specify an app name to activate that app first and capture its window. Requires Screen Recording permission.
This record as markdown: /tools/io-github-heznpc-iconnect/capture-window.md
What capture_window does on Iconnect
AI agents call capture_window to retrieve information from Iconnect without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why capture_window is rated Low
This tool captures visual screen data without side effects, state changes, or destructive operations. While it may reveal sensitive information on screen, the action itself is a read-only retrieval of visual content. It does not execute arbitrary code, move data, delete anything, or commit financial transactions.
From the tool's definition Tool description states it 'Capture[s] a screenshot of the frontmost window' with optional app activation. Screenshots are read operations that retrieve visual data without modifying or deleting any data.
Attacks that exploit this kind of access
The rule that runs capture_window safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For capture_window, this is the rule to start with:
capture_window is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every capture_window call is checked against it from then on.
Questions about capture_window
Capture a screenshot of the frontmost window. Optionally specify an app name to activate that app first and capture its window. Requires Screen Recording permission. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.
Register the Iconnect MCP server in PolicyLayer and add a rule for capture_window: 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 Iconnect. Nothing to install.
capture_window 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_window 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_window. 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_window is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue