ssh_exec · Mcp Ssh Live MCP: Risk & Policy

WHAT IT DOES

What ssh_exec does on Mcp Ssh Live

AI agents invoke ssh_exec to trigger actions in Mcp Ssh Live. 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_exec needs a policy

The name 'ssh_exec' strongly implies executing commands over SSH on a remote system. The server context explicitly describes running remote commands. Even with an empty description, the tool name and server context make it almost certain this tool executes arbitrary remote shell commands, which can have catastrophic blast radius if misused by an AI agent — including destructive operations, data exfiltration, or full…

From the tool's definition Tool name 'ssh_exec' on a server described as enabling 'spawning long-running remote commands' with 'live line-by-line output, signal handling, stdin input'; sibling tools include ssh_run_persistent and ssh_send_stdin, all consistent with remote command…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ssh_exec Rate-limited

ssh_exec 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_exec": {
      "limits": [
        {
          "counter": "ssh_exec_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 Mcp Ssh Live, so you can run agents against it safely.

FAQ

Questions about ssh_exec

What does the ssh_exec tool do? +

ssh_exec. It is categorised as a Execute tool in the Mcp Ssh Live 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_exec? +

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

What risk level is ssh_exec? +

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

Can I rate-limit ssh_exec? +

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

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

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