# force_terminate

Force terminate a running terminal session. ${CMD_PREFIX_DESCRIPTION}

Agent View of the PolicyLayer registry record for `force_terminate`. HTML page: https://policylayer.com/tools/desktop-commander/force-terminate

## Facts

- Tool: `force_terminate`
- Server: Desktop Commander (`wonderwhy-er/DesktopCommanderMCP`) — https://policylayer.com/tools/desktop-commander.md
- Homepage: https://github.com/wonderwhy-er/DesktopCommanderMCP
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "force_terminate",
    "arguments": {}
  }
}
```

## Why force_terminate is rated Critical

Force terminating a terminal session is irreversible — any unsaved state, running processes, or in-progress operations are permanently lost. This cannot be undone, making it Destructive. The 'force' qualifier further implies bypassing normal shutdown procedures, increasing blast radius if misused by an AI agent.

From the tool's own definition: "Force terminate a running terminal session"

## Use case

AI agents call force_terminate to permanently remove resources in Desktop Commander, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Desktop Commander:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "force_terminate"
  ]
}
```

## Other tools on Desktop Commander (10)

- `get_config` — Read — https://policylayer.com/tools/desktop-commander/get-config.md
- `get_file_info` — Read — https://policylayer.com/tools/desktop-commander/get-file-info.md
- `get_recent_tool_calls` — Read — https://policylayer.com/tools/desktop-commander/get-recent-tool-calls.md
- `get_usage_stats` — Read — https://policylayer.com/tools/desktop-commander/get-usage-stats.md
- `kill_process` — Read — https://policylayer.com/tools/desktop-commander/kill-process.md
- `list_processes` — Read — https://policylayer.com/tools/desktop-commander/list-processes.md
- `list_searches` — Read — https://policylayer.com/tools/desktop-commander/list-searches.md
- `create_directory` — Write — https://policylayer.com/tools/desktop-commander/create-directory.md
- `move_file` — Write — https://policylayer.com/tools/desktop-commander/move-file.md
- `set_config_value` — Write — https://policylayer.com/tools/desktop-commander/set-config-value.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=desktop-commander · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/desktop-commander