# kill_app

Force stop an Android app by package name.

Agent View of the PolicyLayer registry record for `kill_app`. HTML page: https://policylayer.com/tools/1193776794-frida-mcp/kill-app

## Facts

- Tool: `kill_app`
- Server: Frida Agent MCP (`1193776794/frida-mcp`) — https://policylayer.com/tools/1193776794-frida-mcp.md
- Homepage: https://github.com/1193776794/frida-mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

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

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

## Why kill_app is rated Critical

Force stopping an app is an irreversible action that terminates the process and any unsaved state is lost. This is more severe than a graceful shutdown and cannot be undone once executed. Misuse could disrupt critical applications running on the target device.

From the tool's own definition: "Force stop an Android app by package name"

## Use case

AI agents call kill_app to permanently remove resources in Frida Agent MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Frida Agent MCP:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "kill_app"
  ]
}
```

## Other tools on Frida Agent MCP (9)

- `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
- `list_apps` — Read — https://policylayer.com/tools/1193776794-frida-mcp/list-apps.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