kill-server

THE RISK

Critical Risk

Why kill-server needs a policy

Killing the ADB server process is an irreversible termination action that immediately stops the ADB daemon, disconnecting all connected Android devices and disrupting any ongoing operations. This cannot be undone without manually restarting the server, and misuse by an AI agent could disrupt all device management operations on the host.

From the tool's definition Kill the ADB server process

Documented attack patterns abuse exactly the kind of access kill-server gives an agent:

POLICY

How to control kill-server

PolicyLayer is an MCP gateway — it sits between your AI agents and ADB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for kill-server:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "kill-server"
  ]
}

kill-server disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register ADB MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More ADB MCP Server tools

Destructive clear-app-data Clear application data for a specific package Destructive clear-logcat 清除设备上的日志缓冲区 Destructive reset-permissions Reset all permissions for a specific package Destructive revoke-permission Revoke a specific permission from an app Destructive rm Remove a file from the Android device Destructive uninstall-apk Uninstall an application from the device Execute start-activity Start an activity using activity manager (am start) Execute start-server Start the ADB server process

All 30 ADB MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in ADB MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about kill-server

What does the kill-server tool do? +

Kill the ADB server process. It is categorised as a Destructive tool in the ADB MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on kill-server? +

Register the ADB MCP Server MCP server in PolicyLayer and add a rule for kill-server: 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 ADB MCP Server. Nothing to install.

What risk level is kill-server? +

kill-server is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit kill-server? +

Yes. Add a rate_limit block to the kill-server 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.

How do I block kill-server completely? +

Set action: deny in the PolicyLayer policy for kill-server. 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.

What MCP server provides kill-server? +

kill-server is provided by the ADB MCP Server MCP server (jiantao88/android-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ADB MCP Server tool call.

Start from ADB MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →