# get_config

Get the complete server configuration as JSON. Config includes fields for: - blockedCommands (array of blocked shell commands) - defaultShell (shell to use for commands) - allowedDirectories (paths the server can access) - fileReadLineLimit (max lines for read_file, default 1000) - fileWriteLineLimit (max lines per write_file call, default 50) - telemetryEnabled (boolean for telemetry opt-in/out) - currentClient (information about the currently connected MCP client) - clientHistory (history of all clients that have connected) - version (version of the DesktopCommander) - systemInfo (operating system and environment details) ${CMD_PREFIX_DESCRIPTION}

Agent View of the PolicyLayer registry record for `get_config`. HTML page: https://policylayer.com/tools/desktop-commander/get-config

## Facts

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

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

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

## Why get_config is rated Low

This is a Read operation as it only retrieves and queries existing configuration data without side effects. However, severity is high because the configuration includes sensitive security settings (blocked commands, allowed directories, rate limits) that could be exploited by an attacker to understand and bypass server restrictions.

From the tool's own definition: "Tool name 'get_config' and description 'Get the complete server configuration as JSON' indicate retrieval of configuration data without modification."

## Use case

AI agents call get_config to retrieve information from Desktop Commander without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_config": {}
  }
}
```

## Other tools on Desktop Commander (10)

- `force_terminate` — Destructive — https://policylayer.com/tools/desktop-commander/force-terminate.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