get_window_list

Get list of all open windows

SERVERMcp Windows SOURCEmukul975/mcp-windows-automation

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mukul975-mcp-windows-automation/get-window-list.md

WHAT IT DOES

What get_window_list does on Mcp Windows

AI agents call get_window_list to retrieve information from Mcp Windows without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_window_list is rated Low

This tool retrieves information about currently open windows on a Windows system. It is purely informational with no capability to modify system state, execute code, delete data, or commit financial transactions. The blast radius of misuse is minimal—an AI agent could only gain visibility into what windows are open, which poses low risk.

From the tool's definition Tool name 'get_window_list' and description 'Get list of all open windows' indicate a query operation that retrieves window state information without modification, execution, or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_window_list safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Windows, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_window_list, this is the rule to start with:

get_window_list Allowed

get_window_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_window_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Windows, apply this rule, and every get_window_list call is checked against it from then on.

FAQ

Questions about get_window_list

What does the get_window_list tool do? +

Get list of all open windows. It is categorised as a Read tool in the Mcp Windows MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_window_list? +

Register the Mcp Windows MCP server in PolicyLayer and add a rule for get_window_list: 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 Windows. Nothing to install.

What risk level is get_window_list? +

get_window_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_window_list? +

Yes. Add a rate_limit block to the get_window_list 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.

How do I block get_window_list completely? +

Set action: deny in the PolicyLayer policy for get_window_list. 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.

What MCP server provides get_window_list? +

get_window_list is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Windows, and thousands of servers like it.

This server

All 441 Mcp Windows tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →