[CRITICAL - OPTIMIZED] Capture comprehensive desktop state with ALL interactive elements (buttons, links, text fields). Returns text-only by default (FAST!). Set use_vision=true to get annotated screenshot saved to file (JPEG compressed, 10x faster than base64). Each element has numbered label fo...
AI agents call get_desktop_state to retrieve information from Windows MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get_desktop_state is a query/introspection tool that retrieves the current state of the desktop and UI elements without side effects. While it could inform harmful subsequent actions, the tool itself only reads and returns state information. It does not execute code, modify data, delete resources, or commit financial transactions.
From the tool's definition Tool 'captures' and 'returns' desktop state information; performs no modifications, deletions, or command execution. Description emphasizes "text-only by default" and "annotated screenshot" retrieval—pure observation capabilities.
Attacks that exploit this kind of access
[CRITICAL - OPTIMIZED] Capture comprehensive desktop state with ALL interactive elements (buttons, links, text fields). Returns text-only by default (FAST!). Set use_vision=true to get annotated screenshot saved to file (JPEG compressed, 10x faster than base64). Each element has numbered label for click_element/type_element. USE THIS TOOL FIRST before any actions!. It is categorised as a Read tool in the Windows MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Windows MCP Server MCP server in PolicyLayer and add a rule for get_desktop_state: 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 Windows MCP Server. Nothing to install.
get_desktop_state 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 get_desktop_state 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 get_desktop_state. 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.
get_desktop_state is provided by the Windows MCP Server MCP server (romeo2badboy-rgb/windows-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 →