ssh_disconnect

THE RISK

Critical Risk

Why ssh_disconnect needs a policy

Disconnecting an SSH session terminates an active connection and any associated running processes or state. This action cannot be undone - the session is destroyed. While a new session could be created, the existing session and any unsaved in-progress work is permanently lost.

From the tool's definition "Disconnect an SSH session" - terminates a persistent SSH session irreversibly

Documented attack patterns abuse exactly the kind of access ssh_disconnect gives an agent:

POLICY

How to control ssh_disconnect

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

policy.json

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

ssh_disconnect 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 SSH 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 SSH MCP Server tools

Execute ssh_cancel_command Cancel currently running MCP command for specified SSH session Execute ssh_exec Execute command on remote server via SSH Execute ssh_poll_task Check status of background task in SSH session Execute ssh_connect Establish SSH connection to a remote server Read ssh_version Get SSH MCP server version and build information Read ssh_get_monitoring_url Get the monitoring URL for an SSH session Read ssh_list_sessions List all active SSH sessions

All 8 SSH 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 SSH 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 ssh_disconnect

What does the ssh_disconnect tool do? +

Disconnect an SSH session. It is categorised as a Destructive tool in the SSH 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 ssh_disconnect? +

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

What risk level is ssh_disconnect? +

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

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

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

ssh_disconnect is provided by the SSH MCP Server MCP server (lightspeeddms/ssh-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SSH MCP Server tool call.

Start from SSH 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 →