list_windows

List all visible windows on the desktop.

SERVERAos SOURCE@hybridlabor-api/aos

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/hybridlabor-api-aos/list-windows.md

WHAT IT DOES

What list_windows does on Aos

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

RISK

Why list_windows is rated Low

This is a read-only operation that enumerates visible windows. It has no side effects, does not execute code, modify data, or interact with window contents. While it could reveal sensitive information about running applications, the blast radius of misuse is limited to information disclosure. Severity is low because window enumeration is a benign operation and the information is already visible on the desktop.

From the tool's definition Tool name is 'list_windows' and description states 'List all visible windows on the desktop' - a pure query operation that retrieves information about open windows without modifying any state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_windows safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, 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 Allowed

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

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

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

FAQ

Questions about list_windows

What does the list_windows tool do? +

List all visible windows on the desktop. It is categorised as a Read tool in the Aos MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_windows? +

Register the Aos 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 Aos. Nothing to install.

What risk level is list_windows? +

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

Can I rate-limit list_windows? +

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.

How do I block list_windows completely? +

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.

What MCP server provides list_windows? +

list_windows is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aos, and thousands of servers like it.

This server

All 719 Aos 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 →