This record as markdown: /tools/ra1nyxin-allcanuse-mcp/list-windows.md
What list_windows does on Allcanuse
AI agents call list_windows to retrieve information from Allcanuse without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_windows is rated Low
Window enumeration is a read-only system probe that retrieves state information about open windows without modifying, executing, or deleting anything. Even in a post-exploitation context, listing windows is reconnaissance-only. Low severity because the blast radius of misuse is limited to information disclosure about the user's current window state.
From the tool's definition Tool name 'list_windows' suggests enumeration/retrieval of window information. Description is empty, but the semantic naming pattern ('list_*') across typical system tools indicates a query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_windows safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Allcanuse, 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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Allcanuse, apply this rule, and every list_windows call is checked against it from then on.
Questions about list_windows
list_windows is a read tool on the Allcanuse MCP server. It is categorised as a Read tool in the Allcanuse MCP Server, which means it retrieves data without modifying state.
Register the Allcanuse 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 Allcanuse. 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 Allcanuse MCP server (ra1nyxin/allcanuse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Allcanuse, and thousands of servers like it.
This server
Across the catalogue