get_top_consumers
Get the top N processes consuming the most CPU or memory.
This record as markdown: /tools/19miha99-system-monitor-mcp/get-top-consumers.md
What get_top_consumers does on Desktop Commander MCP Server
AI agents call get_top_consumers 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_top_consumers is rated Low
This tool retrieves and reports existing system resource consumption metrics. It has no side effects, does not execute code or commands, does not modify data, and does not perform destructive operations. It is a straightforward information retrieval function similar to the sibling tools 'get_battery_status', 'get_cpu_per_core', and 'get_network_stats' on the same server.
From the tool's definition Tool name 'get_top_consumers' and description 'Get the top N processes consuming the most CPU or memory' indicate a read-only query operation that retrieves system monitoring data without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs get_top_consumers 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_top_consumers, this is the rule to start with:
get_top_consumers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Desktop Commander MCP Server, apply this rule, and every get_top_consumers call is checked against it from then on.
Questions about get_top_consumers
Get the top N processes consuming the most CPU or memory. It is categorised as a Read tool in the Desktop Commander MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Desktop Commander MCP Server MCP server in PolicyLayer and add a rule for get_top_consumers: 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 MCP Server. Nothing to install.
get_top_consumers is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_top_consumers 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.
Set action: deny in the PolicyLayer policy for get_top_consumers. 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.
get_top_consumers is provided by the Desktop Commander MCP Server MCP server (19miha99/system-monitor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Desktop Commander MCP Server, and thousands of servers like it.
This server
Across the catalogue