get_process_details

Get detailed information about a specific process by PID.

SERVERDesktop Commander MCP Server SOURCE19miha99/system-monitor-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/19miha99-system-monitor-mcp/get-process-details.md

WHAT IT DOES

What get_process_details does on Desktop Commander MCP Server

AI agents call get_process_details 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.

RISK

Why get_process_details is rated Low

This tool retrieves process information (memory usage, CPU, status, etc.) by process ID. It performs no state changes, creates no data, executes no code, and causes no side effects. While the broader server context shows desktop control capabilities, this specific tool is limited to information gathering.

From the tool's definition Tool name 'get_process_details' and description 'Get detailed information about a specific process by PID' indicate a read-only retrieval operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_process_details Allowed

get_process_details 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_process_details": {}
  }
}

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

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

FAQ

Questions about get_process_details

What does the get_process_details tool do? +

Get detailed information about a specific process by PID. It is categorised as a Read tool in the Desktop Commander MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_process_details? +

Register the Desktop Commander MCP Server MCP server in PolicyLayer and add a rule for get_process_details: 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.

What risk level is get_process_details? +

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

Can I rate-limit get_process_details? +

Yes. Add a rate_limit block to the get_process_details 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_process_details completely? +

Set action: deny in the PolicyLayer policy for get_process_details. 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_process_details? +

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

KEEP EXPLORING

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

This server

All 23 Desktop Commander MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

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