kill_app
Force stop an Android app by package name.
This record as markdown: /tools/1193776794-frida-mcp/kill-app.md
What kill_app does on Frida Agent MCP
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.
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 definition Force stop an Android app by package name
Attacks that exploit this kind of access
The rule that runs kill_app safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frida Agent MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For kill_app, this is the rule to start with:
kill_app is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Frida Agent MCP, apply this rule, and every kill_app call is checked against it from then on.
Questions about kill_app
Force stop an Android app by package name. It is categorised as a Destructive tool in the Frida Agent MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Frida Agent MCP server in PolicyLayer and add a rule for kill_app: 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 Frida Agent MCP. Nothing to install.
kill_app is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the kill_app 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 kill_app. 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.
kill_app is provided by the Frida Agent MCP server (1193776794/frida-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Frida Agent, and thousands of servers like it.
Across the catalogue