AI agents call shell_list_processes to retrieve information from LocalAnt without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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
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.
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.
shell_list_processes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
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 →