Low Risk

list_app_windows

List visible application windows on the desktop.

How to control list_app_windows ↓

What list_app_windows does on Claude Pascal MCP Server

AI agents call list_app_windows to retrieve information from Claude Pascal MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why list_app_windows needs a policy

This tool queries the state of the desktop environment to retrieve a list of visible windows. It performs information retrieval only—no creation, modification, deletion, code execution, or external operations. The action is read-only and non-destructive, placing it squarely in the Read category.

From the tool's definition Tool name 'list_app_windows' and description 'List visible application windows on the desktop' indicate a query/enumeration operation that retrieves window information with no side effects.

Documented attack patterns abuse exactly the kind of access list_app_windows gives an agent:

How to control list_app_windows

PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Pascal MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_app_windows:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_app_windows": {}
  }
}

list_app_windows is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Claude Pascal MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_app_windows

What does the list_app_windows tool do? +

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

How do I enforce a policy on list_app_windows? +

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

What risk level is list_app_windows? +

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

Can I rate-limit list_app_windows? +

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

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

list_app_windows is provided by the Claude Pascal MCP Server MCP server (tina4stack/claude-pascal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude Pascal MCP Server tool call.

Start from Claude Pascal MCP Server, 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.

53 Claude Pascal MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.