List running processes with CPU/memory usage.
AI agents call list_processes to retrieve information from OODA Computer Control without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns data about running processes and their resource consumption. It has no side effects—it does not modify system state, execute commands, delete data, or trigger external operations. It is purely informational, making it a Read category tool with low severity since process enumeration is a passive monitoring activity.
From the tool's definition Tool name 'list_processes' and description 'List running processes with CPU/memory usage' indicate retrieval of system information without modification or execution of commands.
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 OODA Computer Control, 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 running processes with CPU/memory usage. It is categorised as a Read tool in the OODA Computer Control MCP Server, which means it retrieves data without modifying state.
Register the OODA Computer Control 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 OODA Computer Control. 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 OODA Computer Control MCP server (mnehmos/mnehmos.ooda.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OODA Computer Control, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
99 OODA Computer Control tools catalogued and risk-classified — across an index of 43,000+ MCP servers.