# get_usage_stats

Get usage statistics for debugging and analysis. Returns summary of tool usage, success/failure rates, and performance metrics. ${CMD_PREFIX_DESCRIPTION}

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

## Facts

- Tool: `get_usage_stats`
- 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_usage_stats",
    "arguments": {}
  }
}
```

## Why get_usage_stats is rated Low

This tool retrieves and returns diagnostic/analytics data without causing side effects, modifying state, or executing operations. It is a straightforward read operation suitable for debugging and monitoring purposes. The low severity reflects minimal risk even if an AI agent calls it; the worst case is unnecessary API calls that consume resources.

From the tool's own definition: "Tool description states it 'Get usage statistics' and 'Returns summary of tool usage, success/failure rates, and performance metrics' — purely informational retrieval with no modification or execution capability."

## Use case

AI agents call get_usage_stats 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_usage_stats": {}
  }
}
```

## Other tools on Desktop Commander (10)

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