process_list

List all running processes. This is an alias for process_find with an empty pattern.

SERVERJshookmcp SOURCE@jshookmcp/jshook

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/process-list.md

WHAT IT DOES

What process_list does on Jshookmcp

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

RISK

Why process_list is rated Low

Tool reads and enumerates system process data without modifying or executing anything.

From the tool's definition List all running processes. Alias for process_find with empty pattern.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs process_list safely

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

process_list Allowed

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

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

The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every process_list call is checked against it from then on.

FAQ

Questions about process_list

What does the process_list tool do? +

List all running processes. This is an alias for process_find with an empty pattern. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on process_list? +

Register the Jshook MCP server in PolicyLayer and add a rule for process_list: 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 Jshookmcp. Nothing to install.

What risk level is process_list? +

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

Can I rate-limit process_list? +

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

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

process_list is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk → The MCP Attack Database →

Guides

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