activate_window · Uiautomation MCP: Risk & Policy

WHAT IT DOES

What activate_window does on Uiautomation

AI agents invoke activate_window to trigger actions in Uiautomation. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why activate_window needs a policy

Based on the server context of Windows desktop UI automation and the tool name, 'activate_window' likely brings a window to the foreground and gives it focus, which is an external operation/side effect on the desktop environment. This falls under Execute. The description is empty, lowering confidence.

From the tool's definition Tool name 'activate_window' on a server described as enabling UI automation with actions like clicking and typing; description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

activate_window Rate-limited

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.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Uiautomation, so you can run agents against it safely.

FAQ

Questions about activate_window

What does the activate_window tool do? +

activate_window. It is categorised as a Execute tool in the Uiautomation 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 Uiautomation 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 Uiautomation. 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 Uiautomation MCP server (miloira/uiautomation-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.