# get_running_processes

Get list of running processes.

Agent View of the PolicyLayer registry record for `get_running_processes`. HTML page: https://policylayer.com/tools/0x-professor-droidforensics-suite/get-running-processes

## Facts

- Tool: `get_running_processes`
- Server: Android Forensics ADB MCP Server (`0x-professor/droidforensics-suite`) — https://policylayer.com/tools/0x-professor-droidforensics-suite.md
- Homepage: https://github.com/0x-Professor/DroidForensics-Suite
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_running_processes",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Android Forensics ADB MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_running_processes": {}
  }
}
```

## Other tools on Android Forensics ADB MCP Server (57)

- `create_full_backup` — Destructive — https://policylayer.com/tools/0x-professor-droidforensics-suite/create-full-backup.md
- `adb_backup_device` — Execute — https://policylayer.com/tools/0x-professor-droidforensics-suite/adb-backup-device.md
- `adb_connect_device` — Execute — https://policylayer.com/tools/0x-professor-droidforensics-suite/adb-connect-device.md
- `adb_shell_command` — Execute — https://policylayer.com/tools/0x-professor-droidforensics-suite/adb-shell-command.md
- `connect_to_device` — Execute — https://policylayer.com/tools/0x-professor-droidforensics-suite/connect-to-device.md
- `extract_with_root` — Execute — https://policylayer.com/tools/0x-professor-droidforensics-suite/extract-with-root.md
- `reboot_device` — Execute — https://policylayer.com/tools/0x-professor-droidforensics-suite/reboot-device.md
- `generate_app_analysis_report` — Other — https://policylayer.com/tools/0x-professor-droidforensics-suite/generate-app-analysis-report.md
- `adb_devices` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/adb-devices.md
- `adb_pull_data` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/adb-pull-data.md
- `analyze_facebook_messenger` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/analyze-facebook-messenger.md
- `analyze_gmail` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/analyze-gmail.md
- `analyze_instagram` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/analyze-instagram.md
- `analyze_network_connections` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/analyze-network-connections.md
- `analyze_partition_info` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/analyze-partition-info.md
- `analyze_telegram` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/analyze-telegram.md
- `analyze_whatsapp` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/analyze-whatsapp.md
- `capture_dmesg` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/capture-dmesg.md
- `capture_logcat` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/capture-logcat.md
- `check_adb_status` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/check-adb-status.md
- `check_root_status` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/check-root-status.md
- `collect_common_artifacts` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/collect-common-artifacts.md
- `collect_forensic_artifacts` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/collect-forensic-artifacts.md
- `create_timeline` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/create-timeline.md
- `dump_database` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/dump-database.md
- `dump_system_settings` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/dump-system-settings.md
- `extract_app_credentials` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/extract-app-credentials.md
- `extract_backup_to_tar` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/extract-backup-to-tar.md
- `extract_exif_metadata` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/extract-exif-metadata.md
- `extract_media_gallery_metadata` — Read — https://policylayer.com/tools/0x-professor-droidforensics-suite/extract-media-gallery-metadata.md
- …and 27 more: https://policylayer.com/tools/0x-professor-droidforensics-suite.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=0x-professor-droidforensics-suite · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0x-professor-droidforensics-suite