get_temperatures

What get_temperatures does on Desktop Commander MCP Server

AI agents call get_temperatures 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_temperatures is rated Low

This tool only reads system temperature sensor data without causing any side effects, modifications, or state changes. It is a straightforward monitoring/query function that fits the Read category. Severity is low because even if an AI agent misuses this information, it cannot directly harm the system or user data. The confidence is high because the name and description clearly indicate read-only behavior.

From the tool's definition Tool name is 'get_temperatures' and description states it retrieves 'CPU and hardware temperature sensors' — a pure data retrieval operation with no modification, deletion, or execution capability.

The rule that runs get_temperatures 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_temperatures, this is the rule to start with:

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

Questions about get_temperatures