proxmox_docker_execute_command

Execute Docker command on cluster node.

SERVERMCP Proxmox Server SOURCEbsahane/mcp-proxmox

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/bsahane-mcp-proxmox/proxmox-docker-execute-command.md

WHAT IT DOES

What proxmox_docker_execute_command does on MCP Proxmox Server

AI agents invoke proxmox_docker_execute_command to trigger actions in MCP Proxmox 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.

RISK

Why proxmox_docker_execute_command is rated High

This tool runs arbitrary Docker commands on cluster infrastructure. While not immediately destructive (category not Destructive since Docker commands themselves don't inherently delete infrastructure), it is Execute-tier because it triggers external operations whose side effects are argument-dependent.

From the tool's definition Tool name explicitly contains 'execute_command' and description states 'Execute Docker command on cluster node.' This directly triggers external operations (Docker commands) whose effects depend on the arguments provided.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs proxmox_docker_execute_command safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Proxmox Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For proxmox_docker_execute_command, this is the rule to start with:

proxmox_docker_execute_command Rate-limited

proxmox_docker_execute_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": {
    "proxmox_docker_execute_command": {
      "limits": [
        {
          "counter": "proxmox_docker_execute_command_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MCP Proxmox Server, apply this rule, and every proxmox_docker_execute_command call is checked against it from then on.

FAQ

Questions about proxmox_docker_execute_command

What does the proxmox_docker_execute_command tool do? +

Execute Docker command on cluster node. It is categorised as a Execute tool in the MCP Proxmox 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 proxmox_docker_execute_command? +

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

What risk level is proxmox_docker_execute_command? +

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

Can I rate-limit proxmox_docker_execute_command? +

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

Set action: deny in the PolicyLayer policy for proxmox_docker_execute_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 proxmox_docker_execute_command? +

proxmox_docker_execute_command is provided by the MCP Proxmox Server MCP server (bsahane/mcp-proxmox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MCP Proxmox Server, and thousands of servers like it.

This server

All 124 MCP Proxmox Server tools → High-risk tools on this server →

Across the catalogue

claude_execute on Claude Bridge →execute_test_case on Percepta MCP Server →adb_shell_command on Android Forensics ADB MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →