window_list

List all mapped windows with class, title, pid, workspace and geometry. Use to identify targets before acting.

SERVEROmarchy-MCP SOURCEhlsitechio/Omarchy-MCP

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/omarchy-mcp/window-list.md

WHAT IT DOES

What window_list does on Omarchy-MCP

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

RISK

Why window_list is rated Low

Purely informational tool that queries desktop state without side effects.

From the tool's definition List all mapped windows with class, title, pid, workspace and geometry

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs window_list safely

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

window_list Allowed

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": {
    "window_list": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Omarchy-MCP, apply this rule, and every window_list call is checked against it from then on.

FAQ

Questions about window_list

What does the window_list tool do? +

List all mapped windows with class, title, pid, workspace and geometry. Use to identify targets before acting. It is categorised as a Read tool in the Omarchy-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on window_list? +

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

What risk level is window_list? +

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

Can I rate-limit window_list? +

Yes. Add a rate_limit block to the 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 window_list completely? +

Set action: deny in the PolicyLayer policy for 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 window_list? +

window_list is provided by the Omarchy MCP server (hlsitechio/Omarchy-MCP). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Omarchy, and thousands of servers like it.

This server

All 466 Omarchy tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

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