Saari open windows ki list lo
AI agents call desktop_get_windows to retrieve information from Universal Dev MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about currently open windows on the desktop. It is a read-only operation that retrieves data with no side effects, matching the Read category definition. The severity is low because enumeration of open windows poses minimal risk—it cannot modify data, execute code, or cause harm directly. High confidence is assigned due to the clear retrieval nature of the operation.
From the tool's definition Tool name 'desktop_get_windows' and description 'Saari open windows ki list lo' (meaning 'list of all open windows') indicate retrieval of window information without modification or execution of operations.
Attacks that exploit this kind of access
Saari open windows ki list lo. It is categorised as a Read tool in the Universal Dev MCP MCP Server, which means it retrieves data without modifying state.
Register the Universal Dev MCP server in PolicyLayer and add a rule for desktop_get_windows: 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 Universal Dev MCP. Nothing to install.
desktop_get_windows 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 desktop_get_windows 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 desktop_get_windows. 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.
desktop_get_windows is provided by the Universal Dev MCP server (kallusuvaidyam/universal_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 →