ssh_docker_deploy · MCP SSH Server MCP: Risk & Policy

WHAT IT DOES

What ssh_docker_deploy does on MCP SSH Server

AI agents invoke ssh_docker_deploy to trigger actions in MCP SSH Server. 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_docker_deploy needs a policy

Deploying Docker containers is an Execute operation—it triggers external operations (container instantiation, service startup) whose effects depend on arguments (image, configuration, environment variables). While not inherently destructive, container deployment can consume resources, modify system state, and affect running services.

From the tool's definition Tool name 'ssh_docker_deploy' and description 'Deploy Docker containers with working directory context' indicate execution of Docker container deployment operations on remote servers via SSH.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ssh_docker_deploy Rate-limited

ssh_docker_deploy 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_docker_deploy": {
      "limits": [
        {
          "counter": "ssh_docker_deploy_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 Server, so you can run agents against it safely.

FAQ

Questions about ssh_docker_deploy

What does the ssh_docker_deploy tool do? +

Deploy Docker containers with working directory context. It is categorised as a Execute tool in the MCP SSH Server 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_docker_deploy? +

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

What risk level is ssh_docker_deploy? +

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

Can I rate-limit ssh_docker_deploy? +

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

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

ssh_docker_deploy is provided by the MCP SSH Server MCP server (mahathirmuh/mcp-ssh-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.