Delete an existing SSH connection
AI agents call delete_ssh_connection to permanently remove resources in Windows CLI MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes SSH connection configurations. Once deleted, the connection cannot be recovered without manual reconfiguration. This is irreversible data destruction. While not directly damaging to production systems, unauthorized deletion of SSH connections could disrupt legitimate access workflows and represent a denial-of-service vector if an AI agent misuses it maliciously.
From the tool's definition Tool name explicitly uses 'delete' verb; description states 'Delete an existing SSH connection' — irreversible removal of SSH configuration.
Documented attack patterns abuse exactly the kind of access delete_ssh_connection gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Windows CLI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_ssh_connection:
{
"version": "1",
"default": "deny",
"hide": [
"delete_ssh_connection"
]
}delete_ssh_connection disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete an existing SSH connection. It is categorised as a Destructive tool in the Windows CLI MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Windows CLI MCP Server MCP server in PolicyLayer and add a rule for delete_ssh_connection: 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 Windows CLI MCP Server. Nothing to install.
delete_ssh_connection 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 delete_ssh_connection 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 delete_ssh_connection. 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.
delete_ssh_connection is provided by the Windows CLI MCP Server MCP server (simon-ami/win-cli-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 Windows CLI MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
5 Windows CLI MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.