# list_apps

List running applications on the connected device.

Agent View of the PolicyLayer registry record for `list_apps`. HTML page: https://policylayer.com/tools/1193776794-frida-mcp/list-apps

## Facts

- Tool: `list_apps`
- Server: Frida Agent MCP (`1193776794/frida-mcp`) — https://policylayer.com/tools/1193776794-frida-mcp.md
- Homepage: https://github.com/1193776794/frida-mcp
- Risk category: Read (Low risk)
- Registry record: grade D, 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": "list_apps",
    "arguments": {}
  }
}
```

## Why list_apps is rated Low

This tool performs a simple enumeration of running applications on an Android device. It retrieves information (application list) with no side effects, state changes, or code execution. While the broader Frida Agent context involves dynamic analysis and code injection capabilities, this specific tool is a read-only query.

From the tool's own definition: "Tool name 'list_apps' and description 'List running applications on the connected device' indicate a query operation that retrieves data about running processes without modifying or executing anything."

## Use case

AI agents call list_apps to retrieve information from Frida Agent MCP 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 Frida Agent MCP:

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

## Other tools on Frida Agent MCP (9)

- `kill_app` — Destructive — https://policylayer.com/tools/1193776794-frida-mcp/kill-app.md
- `connect` — Execute — https://policylayer.com/tools/1193776794-frida-mcp/connect.md
- `detach` — Execute — https://policylayer.com/tools/1193776794-frida-mcp/detach.md
- `execute` — Execute — https://policylayer.com/tools/1193776794-frida-mcp/execute.md
- `launch_app` — Execute — https://policylayer.com/tools/1193776794-frida-mcp/launch-app.md
- `reconnect` — Execute — https://policylayer.com/tools/1193776794-frida-mcp/reconnect.md
- `spawn_and_inject` — Execute — https://policylayer.com/tools/1193776794-frida-mcp/spawn-and-inject.md
- `get_messages` — Read — https://policylayer.com/tools/1193776794-frida-mcp/get-messages.md
- `logcat` — Read — https://policylayer.com/tools/1193776794-frida-mcp/logcat.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=1193776794-frida-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/1193776794-frida-mcp