List accessible application windows in the isolated session.
AI agents call list_windows to retrieve information from Kwin 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 currently open windows in a KWin session without modifying, creating, or deleting any data or triggering external operations. It is a pure information-gathering action, making it a Read category tool with low severity since window listing poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'list_windows' and description 'List accessible application windows in the isolated session' indicate a query/retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_windows gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kwin, and nothing reaches the server without passing your rules. This is the rule we recommend for list_windows:
{
"version": "1",
"default": "deny",
"tools": {
"list_windows": {}
}
}list_windows 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.
List accessible application windows in the isolated session. It is categorised as a Read tool in the Kwin MCP Server, which means it retrieves data without modifying state.
Register the Kwin 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 Kwin. 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 Kwin MCP server (isac322/kwin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kwin, 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.
30 Kwin tools catalogued and risk-classified — across an index of 43,000+ MCP servers.