repl_kill

Terminate a REPL session (SIGTERM, then SIGKILL).

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/alexgladkov-claude-in-mobile/repl-kill.md

WHAT IT DOES

What repl_kill does on Claude Mobile

AI agents call repl_kill to permanently remove resources in Claude Mobile, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why repl_kill is rated Critical

The tool forcibly terminates a running REPL session using SIGTERM followed by SIGKILL. Killing a process is irreversible — the session and any unsaved state are permanently destroyed. This maps to Destructive category. Severity is high because an AI agent misusing this could terminate critical running processes, losing unsaved work or disrupting automation flows.

From the tool's definition Terminate a REPL session (SIGTERM, then SIGKILL)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs repl_kill safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Mobile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For repl_kill, this is the rule to start with:

repl_kill Hidden

repl_kill is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "repl_kill"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Mobile, apply this rule, and every repl_kill call is checked against it from then on.

FAQ

Questions about repl_kill

What does the repl_kill tool do? +

Terminate a REPL session (SIGTERM, then SIGKILL). It is categorised as a Destructive tool in the Claude Mobile 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 repl_kill? +

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

What risk level is repl_kill? +

repl_kill 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 repl_kill? +

Yes. Add a rate_limit block to the repl_kill 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 repl_kill completely? +

Set action: deny in the PolicyLayer policy for repl_kill. 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 repl_kill? +

repl_kill is provided by the Claude Mobile MCP server (alexgladkov/claude-in-mobile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Mobile, and thousands of servers like it.

This server

All 198 Claude Mobile tools → Critical-risk tools on this server →

Across the catalogue

kill_ftp_session on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →