// SCAN REPORT

Desktop Commander MCP Server

23 tools. 7 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 2 Oct 2026

7 can modify or destroy data

16 read-only

23 tools total

Community server · catalogue entry checked 02/10/2026

How to control Desktop Commander MCP Server ↓

TOOL MAP

What Desktop Commander MCP Server exposes to your agents

Read (16) Write / Execute (6) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Desktop Commander MCP Server tools

Destructive · High kill_process Killing a process is an irreversible action: any unsaved data in that process is lost, and critical system or application processes being killed can cause crashes or service outages. Execute · High launch_application Launching applications is an Execute-category action because it triggers external operations whose effects depend on arguments (which application is launched, with what parameters). Execute · Low set_window_state This tool triggers an external desktop operation (changing window state) that affects the running environment. Execute · Medium focus_window Based on the tool name and server context ('full control over your desktop', 'manage windows'), focus_window likely brings a specific window to the foreground and gives it input focus.

7 of Desktop Commander MCP Server's 23 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Desktop Commander MCP Server

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

Deny destructive operations

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

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

Rate limit write operations

{
  "close_window": {
    "limits": [
      {
        "counter": "close_window_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "arrange_window": {
    "limits": [
      {
        "counter": "arrange_window_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 Desktop Commander MCP Server — 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 DESKTOP COMMANDER →

Instant setup, no code required.

FULL CATALOGUE

All 23 Desktop Commander MCP Server tools

DESTRUCTIVE 1 tools

Destructive kill_process Terminate or kill a process by PID.

EXECUTE 3 tools

Execute focus_window focus_window Execute launch_application launch_application Execute set_window_state Minimize, maximize, or restore a window.

WRITE 3 tools

Write close_window Close a window gracefully by sending WM_CLOSE. Write send_notification Send a desktop toast notification. Write write_clipboard Write text to the system clipboard.

READ 16 tools

Read arrange_window arrange_window Read capture_screenshot capture_screenshot Read find_process_by_port Find which process is using a specific network port. Read get_battery_status Get battery status (for laptops): charge percentage, time remaining, power source. Read get_cpu_per_core Get CPU usage percentage for each individual core. Read get_display_info Get display/monitor information: resolution, DPI, number of monitors. Read get_network_stats Get network interface statistics: bytes sent/received, active connections summary. Read get_process_details Get detailed information about a specific process by PID. Read get_startup_programs List programs configured to run at Windows startup. Read get_system_overview Get a high-level overview of the system: CPU, RAM, disk, swap, and uptime. Read get_temperatures Get CPU and hardware temperature sensors (Linux/macOS). Read get_top_consumers Get the top N processes consuming the most CPU or memory. Read list_processes list_processes Read list_windows list_windows Read read_clipboard Read the current text content from the system clipboard. Read search_installed_apps search_installed_apps

EXPLORE

Related servers

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

FAQ

Questions about Desktop Commander MCP Server

Can an AI agent delete data through the Desktop Commander MCP Server MCP server? +

Yes. The Desktop Commander MCP Server server exposes 1 destructive tools including kill_process. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Desktop Commander MCP Server? +

The Desktop Commander MCP Server server has 3 write tools including close_window, send_notification, write_clipboard. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Desktop Commander MCP Server.

How many tools does the Desktop Commander MCP Server MCP server expose? +

23 tools across 3 categories: Execute, Read, Write. 16 are read-only. 7 can modify, create, or delete data.

How do I enforce a policy on Desktop Commander MCP Server? +

Register the Desktop Commander MCP Server 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 Desktop Commander MCP Server tool call.

Deterministic rules across all 23 Desktop Commander MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON DESKTOP COMMANDER →

Instant setup, no code required.

23 Desktop Commander MCP Server tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Desktop Commander MCP Server's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →