shell_list_processes

List tracked long-running processes.

SERVERLocalAnt SOURCEyuga-hashimoto/localant

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/yuga-hashimoto-localant/shell-list-processes.md

WHAT IT DOES

What shell_list_processes does on LocalAnt

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

RISK

Why shell_list_processes is rated Low

This tool retrieves information about running processes without modifying, executing, or deleting anything. It is a read-only operation that gathers system state data. Severity is low because exposing process lists has minimal direct security impact—it provides visibility into system state but does not enable harmful actions by itself.

From the tool's definition Tool name 'shell_list_processes' and description 'List tracked long-running processes' indicate a query/retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs shell_list_processes safely

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

shell_list_processes Allowed

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

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

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

FAQ

Questions about shell_list_processes

What does the shell_list_processes tool do? +

List tracked long-running processes. It is categorised as a Read tool in the LocalAnt MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on shell_list_processes? +

Register the LocalAnt MCP server in PolicyLayer and add a rule for shell_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 LocalAnt. Nothing to install.

What risk level is shell_list_processes? +

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

Can I rate-limit shell_list_processes? +

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

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

shell_list_processes is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on LocalAnt, and thousands of servers like it.

This server

All 216 LocalAnt tools →

Across the catalogue

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

Guides

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