list_processes

List running processes with optional filters

Server Windows Diagnostics MCP Server jackalterman/windows-diagnostic-mcp-server
Category Read
Risk class Low
Parameters 00 required

What list_processes does on Windows Diagnostics MCP Server

AI agents call list_processes to retrieve information from Windows Diagnostics MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list_processes needs a policy

This tool retrieves information about running processes, which is a non-destructive, side-effect-free diagnostic query. While process information could theoretically be used to inform harmful decisions, the tool itself only reads and filters existing data. No execution, modification, deletion, or financial operations are performed. This aligns with the 'Read' category for diagnostic system queries.

From the tool's definition Tool name 'list_processes' and description 'List running processes with optional filters' indicate data retrieval only. The verb 'list' and 'with optional filters' are characteristic of Read operations that query system state without modification or execution.

Questions about list_processes

What does the list_processes tool do? +

List running processes with optional filters. It is categorised as a Read tool in the Windows Diagnostics MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_processes? +

Register the Windows Diagnostics MCP Server MCP server in PolicyLayer and add a rule for list_processes: 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 Windows Diagnostics MCP Server. Nothing to install.

What risk level is list_processes? +

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

Can I rate-limit list_processes? +

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

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

list_processes is provided by the Windows Diagnostics MCP Server MCP server (jackalterman/windows-diagnostic-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.