get_cpu_per_core

What get_cpu_per_core does on Desktop Commander MCP Server

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

Why get_cpu_per_core is rated Low

This tool queries CPU metrics and returns data without side effects. It does not modify system state, execute code, delete data, or move money. The server provides 'full control over your desktop' but this specific tool is limited to reading CPU performance statistics, consistent with other sibling tools like 'get_battery_status', 'get_display_info', and 'get_network_stats' which are all informational reads.

From the tool's definition Tool name 'get_cpu_per_core' and description 'Get CPU usage percentage for each individual core' indicate a read-only operation that retrieves system monitoring data without modification or execution of commands.

The rule that runs get_cpu_per_core safely

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

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

Questions about get_cpu_per_core