ssh_connect_with_jump_command · Ssh Mcp Server Secured MCP

WHAT IT DOES

What ssh_connect_with_jump_command does on Ssh Mcp Server Secured

AI agents invoke ssh_connect_with_jump_command to trigger actions in Ssh Mcp Server Secured. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why ssh_connect_with_jump_command needs a policy

This tool establishes an SSH connection and executes a jump command to enter a nested interactive shell. Running arbitrary commands in an interactive shell on a remote host is an Execute-category action with high severity, as a misused or malicious jump command could alter system state, escalate privileges, or cause damage on remote infrastructure.

From the tool's definition 'SSH into a host, then execute a jump command to enter a nested interactive shell'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ssh_connect_with_jump_command Rate-limited

ssh_connect_with_jump_command stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ssh_connect_with_jump_command": {
      "limits": [
        {
          "counter": "ssh_connect_with_jump_command_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ssh Mcp Server Secured, so you can run agents against it safely.

FAQ

Questions about ssh_connect_with_jump_command

What does the ssh_connect_with_jump_command tool do? +

SSH into a host, then execute a jump command to enter a nested interactive shell. It is categorised as a Execute tool in the Ssh Mcp Server Secured MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ssh_connect_with_jump_command? +

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

What risk level is ssh_connect_with_jump_command? +

ssh_connect_with_jump_command is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ssh_connect_with_jump_command? +

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

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

ssh_connect_with_jump_command is provided by the Ssh Mcp Server Secured MCP server (marian-craciunescu/ssh-mcp-server-secured). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.