get_usage_stats

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

SERVERDesktop Commander SOURCEwonderwhy-er/DesktopCommanderMCP

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/desktop-commander/get-usage-stats.md

WHAT IT DOES

What get_usage_stats does on Desktop Commander

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.

RISK

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 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_usage_stats safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Desktop Commander, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_usage_stats, this is the rule to start with:

get_usage_stats Allowed

get_usage_stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_usage_stats": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Desktop Commander, apply this rule, and every get_usage_stats call is checked against it from then on.

FAQ

Questions about get_usage_stats

What does the get_usage_stats tool do? +

Get usage statistics for debugging and analysis. Returns summary of tool usage, success/failure rates, and performance metrics. ${CMD_PREFIX_DESCRIPTION}. It is categorised as a Read tool in the Desktop Commander MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_usage_stats? +

Register the Desktop Commander MCP server in PolicyLayer and add a rule for get_usage_stats: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Desktop Commander. Nothing to install.

What risk level is get_usage_stats? +

get_usage_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_usage_stats? +

Yes. Add a rate_limit block to the get_usage_stats rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block get_usage_stats completely? +

Set action: deny in the PolicyLayer policy for get_usage_stats. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides get_usage_stats? +

get_usage_stats is provided by the Desktop Commander MCP server (wonderwhy-er/DesktopCommanderMCP). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Desktop Commander, and thousands of servers like it.

This server

All 11 Desktop Commander tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →