get_running_processes
Get list of running processes.
This record as markdown: /tools/0x-professor-droidforensics-suite/get-running-processes.md
What get_running_processes does on Android Forensics ADB MCP Server
AI agents call get_running_processes to retrieve information from Android Forensics ADB 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 get_running_processes is rated Low
This tool retrieves and lists currently running processes on an Android device. It is a read-only operation that queries system state with no side effects, no data modification, and no capability to execute commands or delete data. While it provides forensic insight into device activity, the act of listing processes causes no changes to the device state.
From the tool's definition Tool name 'get_running_processes' and description 'Get list of running processes' indicate a query operation that retrieves process information without modifying, deleting, or executing arbitrary code on the device.
Attacks that exploit this kind of access
The rule that runs get_running_processes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Android Forensics ADB MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_running_processes, this is the rule to start with:
get_running_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 Android Forensics ADB MCP Server, apply this rule, and every get_running_processes call is checked against it from then on.
Questions about get_running_processes
Get list of running processes. It is categorised as a Read tool in the Android Forensics ADB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Android Forensics ADB MCP Server MCP server in PolicyLayer and add a rule for get_running_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 Android Forensics ADB MCP Server. Nothing to install.
get_running_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 get_running_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 get_running_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.
get_running_processes is provided by the Android Forensics ADB MCP Server MCP server (0x-professor/droidforensics-suite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Android Forensics ADB MCP Server, and thousands of servers like it.
This server
Across the catalogue