list_processes

List all running processes started by the agent

SERVERCode MCP Server SOURCEagentics-ai/code-mcp

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/agentics-ai-code-mcp/list-processes.md

WHAT IT DOES

What list_processes does on Code MCP Server

AI agents call list_processes to retrieve information from Code 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 list_processes is rated Low

The tool retrieves and enumerates process information without modifying, executing, or deleting anything. It is fundamentally a Read operation. Severity is medium rather than low because process enumeration could reveal sensitive operational context (e.g., credentials in command-line arguments, internal service names) that an agent might exfiltrate; however, the tool itself performs no destructive or executable…

From the tool's definition Tool name is 'list_processes' and description states it 'List all running processes started by the agent' — a read-only query operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_processes safely

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

list_processes Allowed

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

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

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

FAQ

Questions about list_processes

What does the list_processes tool do? +

List all running processes started by the agent. It is categorised as a Read tool in the Code MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_processes? +

Register the Code 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 Code 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 Code MCP Server MCP server (agentics-ai/code-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

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

This server

All 73 Code MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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