proxmox_docker_swarm_status

Get Docker Swarm cluster status and information.

SERVERMCP Proxmox Server SOURCEbsahane/mcp-proxmox

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/bsahane-mcp-proxmox/proxmox-docker-swarm-status.md

WHAT IT DOES

What proxmox_docker_swarm_status does on MCP Proxmox Server

AI agents call proxmox_docker_swarm_status to retrieve information from MCP Proxmox Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why proxmox_docker_swarm_status is rated Low

This tool retrieves and queries Docker Swarm cluster status and information. The verb 'Get' and the informational nature of 'status and information' clearly indicate a read operation with no side effects. While it operates within a Proxmox infrastructure management context, it only observes the state of Docker Swarm clusters without modifying, executing, or destroying any resources.

From the tool's definition Tool name 'proxmox_docker_swarm_status' and description 'Get Docker Swarm cluster status and information' indicate read-only querying of status/information without modification, creation, deletion, or execution of commands.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs proxmox_docker_swarm_status 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_swarm_status, this is the rule to start with:

proxmox_docker_swarm_status Allowed

proxmox_docker_swarm_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "proxmox_docker_swarm_status": {}
  }
}

ALLOW ONLY 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_swarm_status call is checked against it from then on.

FAQ

Questions about proxmox_docker_swarm_status

What does the proxmox_docker_swarm_status tool do? +

Get Docker Swarm cluster status and information. It is categorised as a Read tool in the MCP Proxmox Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on proxmox_docker_swarm_status? +

Register the MCP Proxmox Server MCP server in PolicyLayer and add a rule for proxmox_docker_swarm_status: 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_swarm_status? +

proxmox_docker_swarm_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit proxmox_docker_swarm_status? +

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

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

proxmox_docker_swarm_status 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 →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →