list_processes
A read tool on the 1Panel MCP server.
This record as markdown: /tools/eaveluo-1panel-mcp/list-processes.md
What list_processes does on 1Panel MCP Server
AI agents call list_processes to retrieve information from 1Panel MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_processes is rated Low
The tool retrieves and displays process information without modifying, executing, or deleting anything. Listing processes is a read-only operation that merely queries system state. While the broader server can execute code and manage infrastructure, this specific tool is purely informational.
From the tool's definition Tool name is 'list_processes' and description is 'List processes'. This is a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_processes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 1Panel 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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 1Panel MCP Server, apply this rule, and every list_processes call is checked against it from then on.
Questions about list_processes
list_processes is a read tool on the 1Panel MCP Server MCP server. It is categorised as a Read tool in the 1Panel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 1Panel 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 1Panel MCP Server. Nothing to install.
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 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 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.
list_processes is provided by the 1Panel MCP Server MCP server (eaveluo/1panel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 1Panel MCP Server, and thousands of servers like it.
This server
Across the catalogue