// SCAN REPORT

MCP Windows Desktop Automation

50 tools. 37 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 11 Jun 2026

37 can modify or destroy data

13 read-only

50 tools total

Community server · catalogue entry verified 11/06/2026

How to control MCP Windows Desktop Automation ↓

TOOL MAP

What MCP Windows Desktop Automation exposes to your agents

Read (13) Write / Execute (34) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous MCP Windows Desktop Automation tools

Destructive · High processClose AutoIt's ProcessClose function forcibly terminates a running process, which is an irreversible action — it cannot be undone once the process is killed. Destructive · Critical shutdown A shutdown operation is effectively irreversible in the moment — it terminates all running processes and powers off or restarts the system. Execute · High processWait This tool triggers/waits for external process state changes, which is a form of process control and external operation execution. Execute · High processWaitClose Process termination is an Execute-level action because it triggers external operations (process control) whose consequences depend on arguments (process name/ID).

37 of MCP Windows Desktop Automation's 50 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control MCP Windows Desktop Automation

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Windows Desktop Automation, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "processClose": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Cap read operations

{
  "clipGet": {
    "limits": [
      {
        "counter": "clipget_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register MCP Windows Desktop Automation — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MCP WINDOWS DESKTOP AUTOMATION →

Free to start. No card required.

FULL CATALOGUE

All 50 MCP Windows Desktop Automation tools

DESTRUCTIVE 2 tools

Destructive processClose processClose Destructive shutdown shutdown

EXECUTE 34 tools

Execute processWait processWait Execute processWaitClose processWaitClose Execute run run Execute runAs runAs Execute runAsWait runAsWait Execute runWait runWait Execute winWait winWait Execute winWaitActive winWaitActive Execute winWaitClose winWaitClose Execute controlShow controlShow Execute autoItSetOption autoItSetOption Execute clipPut clipPut Execute controlClick controlClick Execute controlClickByHandle controlClickByHandle Execute controlCommand controlCommand Execute controlFocus controlFocus Execute controlHide controlHide Execute controlMove controlMove Execute controlSend controlSend Execute controlSetText controlSetText Execute mouseClick mouseClick Execute mouseClickDrag mouseClickDrag Execute mouseDown mouseDown Execute mouseMove mouseMove Execute mouseUp mouseUp Execute mouseWheel mouseWheel Execute processSetPriority processSetPriority Execute send send Execute winActivate winActivate Execute winActivateByHandle winActivateByHandle Execute winClose winClose Execute winMove winMove Execute winSetState winSetState

READ 13 tools

Read clipGet clipGet Read controlGetHandle controlGetHandle Read controlGetPos controlGetPos Read controlGetText controlGetText Read mouseGetCursor mouseGetCursor Read mouseGetPos mouseGetPos Read winGetHandle winGetHandle Read winGetPos winGetPos Read winGetText winGetText Read winGetTitle winGetTitle Read processExists processExists Read winActive winActive Read winExists winExists

OTHER 1 tools

Other opt opt

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about MCP Windows Desktop Automation

Can an AI agent delete data through the MCP Windows Desktop Automation MCP server? +

Yes. The MCP Windows Desktop Automation server exposes 2 destructive tools including processClose, shutdown. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How many tools does the MCP Windows Desktop Automation MCP server expose? +

50 tools across 3 categories: Execute, Read, Write. 13 are read-only. 37 can modify, create, or delete data.

How do I enforce a policy on MCP Windows Desktop Automation? +

Register the MCP Windows Desktop Automation MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every MCP Windows Desktop Automation tool call.

Deterministic rules across all 50 MCP Windows Desktop Automation tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MCP WINDOWS DESKTOP AUTOMATION →

Free to start. No card required.

50 MCP Windows Desktop Automation tools catalogued and risk-classified — across an index of 43,000+ MCP servers.