AI agents use update_ssh_connection to create or update resources in Windows CLI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Windows CLI MCP Server environment.
This tool performs a write/update operation on SSH connection configurations. It is classified as Write rather than Execute because it modifies configuration data reversibly, not because it runs arbitrary commands.
From the tool's definition Tool name and description: 'Update an existing SSH connection' - modifies an existing SSH connection configuration. This is a reversible modification operation that changes connection parameters without deleting data.
Documented attack patterns abuse exactly the kind of access update_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 update_ssh_connection:
{
"version": "1",
"default": "deny",
"tools": {
"update_ssh_connection": {
"limits": [
{
"counter": "update_ssh_connection_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_ssh_connection stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update an existing SSH connection. It is categorised as a Write tool in the Windows CLI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Windows CLI MCP Server MCP server in PolicyLayer and add a rule for update_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.
update_ssh_connection is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_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.