# desktop-commander

> desktop-commander is a community-maintained MCP server from wonderwhy-er. Anomity scores its risk at 100 out of 100 (critical). It matches 3 dangerous capability combinations.

- **Canonical URL:** https://catalog.anomity.ai/mcp/desktop-commander
- **Kind:** MCP server
- **Publisher:** wonderwhy-er
- **Trust level:** community
- **Risk score:** 100/100 (critical)
- **Last updated:** 2026-11-01
- **JSON:** https://catalog.anomity.ai/api/entries/mcp/desktop-commander

## Why it scored 100

The score starts at the catalog's neutral base of 50 and moves only through the signals below. The formula is published at https://catalog.anomity.ai/about — there is no model and no hidden heuristic.

| Signal | Contribution | Severity | Evidence |
| --- | --- | --- | --- |
| Established community project | -10 | trust offset |  |
| 2 high-risk capabilities: shell:execute, filesystem:write | +20 | critical |  |
| Data exfiltration risk (high) | +15 | high | Shell execution combined with outbound network access can exfiltrate arbitrary data from the machine. |
| Persistence + execution risk (medium) | +5 | medium | Shell execution plus filesystem write means the agent can plant persistent backdoors (e.g. modifying startup scripts). |
| Full-control risk (critical) | +25 | critical | Shell + filesystem write + network is effectively a remote shell on the employee machine. |

Clamped result: **100/100**, band **critical**.

## Capabilities

| Capability | Name | Security implication |
| --- | --- | --- |
| `shell:execute` | Shell execution | Can run arbitrary shell commands. Combined with network access this becomes effectively a remote shell. |
| `filesystem:read` | Filesystem read | Can read files on the host system. Used for context, indexing, or analysis. |
| `filesystem:write` | Filesystem write | Can create, edit, or delete files on the host system. High-impact capability — anything from helpful edits to planting persistence. |
| `network:outbound` | Outbound network | Can make outbound network requests. Required for hosted model providers and remote APIs; also the path for data exfiltration if combined with read access. |

## Dangerous combinations matched

### Data exfiltration risk (high)

Shell execution combined with outbound network access can exfiltrate arbitrary data from the machine.

Capabilities: `shell:execute`, `network:outbound`

### Persistence + execution risk (medium)

Shell execution plus filesystem write means the agent can plant persistent backdoors (e.g. modifying startup scripts).

Capabilities: `shell:execute`, `filesystem:write`

### Full-control risk (critical)

Shell + filesystem write + network is effectively a remote shell on the employee machine.

Capabilities: `shell:execute`, `filesystem:write`, `network:outbound`

## Related MCP servers

- [angular-cli](https://catalog.anomity.ai/mcp/angular-cli) — risk 75 (high)
- [task-master](https://catalog.anomity.ai/mcp/task-master) — risk 75 (high)
- [motherduck](https://catalog.anomity.ai/mcp/motherduck) — risk 70 (high)
- [dbt](https://catalog.anomity.ai/mcp/dbt) — risk 60 (high)
- [claude-code-mcp-serve](https://catalog.anomity.ai/mcp/claude-code-mcp-serve) — risk 35 (medium)
- [codex-node-repl](https://catalog.anomity.ai/mcp/codex-node-repl) — risk 35 (medium)

---

Source: Anomity Security Database (https://catalog.anomity.ai/). Scoring methodology: https://catalog.anomity.ai/about. Machine-readable index: https://catalog.anomity.ai/llms.txt · https://catalog.anomity.ai/openapi.json