activate_window

THE RISK

High Risk

Why activate_window needs a policy

This tool triggers an external GUI operation — changing window focus/z-order on the desktop. It has side effects on the desktop environment (altering which window is active/foreground), making it an Execute action. Misuse could be used to manipulate UI context for follow-on automation attacks, but blast radius is moderate since it only changes focus without directly destroying data or moving money.

From the tool's definition Activates (brings to the front) the first window matching the title

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

POLICY

How to control activate_window

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 activate_window:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "activate_window": {
      "limits": [
        {
          "counter": "activate_window_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

activate_window stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register PyMCPAutoGUI — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More PyMCPAutoGUI tools

Destructive close_window Closes the first window matching the title. Execute alert alert Execute click click Execute confirm confirm Execute drag_rel drag_rel Execute drag_to drag_to Execute hotkey hotkey Execute key_down Presses and holds down the specified keyboard key.

All 34 PyMCPAutoGUI tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in PyMCPAutoGUI → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about activate_window

What does the activate_window tool do? +

Activates (brings to the front) the first window matching the title. It is categorised as a Execute tool in the PyMCPAutoGUI MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on activate_window? +

Register the PyMCPAutoGUI MCP server in PolicyLayer and add a rule for activate_window: 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 activate_window? +

activate_window is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit activate_window? +

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

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

activate_window 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.

CHECK YOUR STACK →