Capture a specific window by title (partial match)
AI agents call screenshot_window to retrieve information from MCP Desktop Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Screenshots are read operations that capture the current state of a window without side effects, modifications, or execution of code. The tool has no destructive, financial, or executable impact—it only retrieves visual information from the desktop. Severity is low because screenshot data could contain sensitive information, but the tool itself performs no harmful actions on the system.
From the tool's definition Tool name 'screenshot_window' and description 'Capture a specific window by title' indicate it retrieves visual data from the screen without modifying or executing operations.
Attacks that exploit this kind of access
Capture a specific window by title (partial match). It is categorised as a Read tool in the MCP Desktop Tools MCP Server, which means it retrieves data without modifying state.
Register the MCP Desktop Tools MCP server in PolicyLayer and add a rule for screenshot_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 MCP Desktop Tools. Nothing to install.
screenshot_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 screenshot_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 screenshot_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.
screenshot_window is provided by the MCP Desktop Tools MCP server (k1ta141k/mcp-desktop-tools). 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 →