AI agents call get_window_list to retrieve information from MCP Windows without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about open windows without modifying, executing operations on them, or causing destructive changes. The 'get_' prefix is a standard convention for read-only operations. Even though the description is missing, the naming convention and context strongly indicate a non-destructive data retrieval operation.
From the tool's definition Tool name 'get_window_list' indicates a read operation that queries the list of open windows on the system. The description is empty, but the function name clearly indicates a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_window_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Windows, and nothing reaches the server without passing your rules. This is the rule we recommend for get_window_list:
{
"version": "1",
"default": "deny",
"tools": {
"get_window_list": {}
}
}get_window_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_window_list. It is categorised as a Read tool in the MCP Windows MCP Server, which means it retrieves data without modifying state.
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.
get_window_list 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_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.
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.
get_window_list is provided by the MCP Windows MCP server (secretiveshell/mcp-windows). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Windows, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
28 MCP Windows tools catalogued and risk-classified — across an index of 43,000+ MCP servers.