List all tracked background processes and their metadata (PID, command, log paths).
AI agents call list_processes to retrieve information from Pwno without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves process information for inspection only. It queries existing state without creating, modifying, deleting, or executing anything. While the server context involves debugging and binary research (potentially sensitive), this specific tool is informational and read-only, carrying minimal risk of misuse by an agent—it neither executes code nor modifies system state.
From the tool's definition Tool description explicitly states it 'List[s] all tracked background processes and their metadata (PID, command, log paths)' — a pure query operation with no modification or execution.
Documented attack patterns abuse exactly the kind of access list_processes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pwno, and nothing reaches the server without passing your rules. This is the rule we recommend for list_processes:
{
"version": "1",
"default": "deny",
"tools": {
"list_processes": {}
}
}list_processes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all tracked background processes and their metadata (PID, command, log paths). It is categorised as a Read tool in the Pwno MCP Server, which means it retrieves data without modifying state.
Register the Pwno 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 Pwno. 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 Pwno MCP server (pwno-io/pwno-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 Pwno tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 Pwno tools catalogued and risk-classified — across an index of 42,500+ MCP servers.