Critical Risk →

deleteConnection

Deletes a saved SSH connection.

How to control deleteConnection ↓

AI agents call deleteConnection to permanently remove resources in Mcp Ssh — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

This tool permanently removes a stored SSH connection configuration, which cannot be automatically recovered. While not as critical as deleting live system data, it is irreversible and causes loss of saved connection state. The high severity reflects that an AI agent inadvertently deleting connection configurations could disrupt workflows and require manual reconfiguration.

From the tool's definition Tool name 'deleteConnection' and description 'Deletes a saved SSH connection' explicitly indicate irreversible deletion of configuration data.

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

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "deleteConnection"
  ]
}

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

  1. Create a free account and register Mcp Ssh — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the deleteConnection tool do? +

Deletes a saved SSH connection. It is categorised as a Destructive tool in the Mcp Ssh 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 deleteConnection? +

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

What risk level is deleteConnection? +

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

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

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

deleteConnection is provided by the Mcp Ssh MCP server (shuakami/mcp-ssh). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Ssh tool call.

Deterministic rules across all 23 Mcp Ssh tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

23 Mcp Ssh tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.