Low Risk

get_windows_with_title

get_windows_with_title

How to control get_windows_with_title ↓

What get_windows_with_title does on PyMCPAutoGUI

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

Low Risk

Why get_windows_with_title needs a policy

This tool retrieves window metadata by title pattern, producing no side effects. It queries the desktop GUI state to identify windows, similar to list or search operations. Although the description is empty (reducing confidence slightly), the function name and context of sibling tools strongly indicate a read-only query. Even if misused, it cannot cause damage—it only retrieves information about open windows.

From the tool's definition Tool name 'get_windows_with_title' suggests retrieving window information; sibling tools include 'get_active_window' and 'get_all_titles' which are clearly Read operations; no description provided but naming pattern indicates a query/retrieval function.

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

How to control get_windows_with_title

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

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

get_windows_with_title 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 PyMCPAutoGUI — 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 get_windows_with_title

What does the get_windows_with_title tool do? +

get_windows_with_title. It is categorised as a Read tool in the PyMCPAutoGUI MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_windows_with_title? +

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

What risk level is get_windows_with_title? +

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

Can I rate-limit get_windows_with_title? +

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

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

get_windows_with_title is provided by the PyMCPAutoGUI MCP server (kitfactory/pymcpautogui). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PyMCPAutoGUI tool call.

Start from PyMCPAutoGUI, 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.

34 PyMCPAutoGUI 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.