list_windows
A read tool on the Desktop Commander MCP server.
This record as markdown: /tools/19miha99-system-monitor-mcp/list-windows.md
What list_windows does on Desktop Commander MCP Server
AI agents call list_windows to retrieve information from Desktop Commander MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_windows is rated Low
This tool retrieves/enumerates open windows on the desktop without modifying them. It is a Read operation. Severity is medium rather than low because window lists could reveal sensitive application activity to an AI agent, but there are no destructive or execution implications. Confidence is high due to clear naming convention and server context, despite the empty description.
From the tool's definition Tool name 'list_windows' indicates retrieval of window information. Server description confirms it 'monitor system resources' and 'manage windows', with sibling tools like 'get_process_details', 'get_display_info' that are clearly Read operations.
Attacks that exploit this kind of access
The rule that runs list_windows safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Desktop Commander MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_windows, this is the rule to start with:
list_windows 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 Desktop Commander MCP Server, apply this rule, and every list_windows call is checked against it from then on.
Questions about list_windows
list_windows is a read tool on the Desktop Commander MCP Server MCP server. It is categorised as a Read tool in the Desktop Commander MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Desktop Commander MCP Server MCP server in PolicyLayer and add a rule for list_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 Desktop Commander MCP Server. Nothing to install.
list_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 list_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 list_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.
list_windows is provided by the Desktop Commander MCP Server MCP server (19miha99/system-monitor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Desktop Commander MCP Server, and thousands of servers like it.
This server
Across the catalogue