proxmox_docker_service_logs

Get Docker Swarm service logs.

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-service-logs.md

WHAT IT DOES

What proxmox_docker_service_logs does on MCP Proxmox Server

AI agents call proxmox_docker_service_logs 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_service_logs is rated Low

This tool retrieves historical log data from Docker Swarm services. Reading logs is a non-destructive, informational operation that does not modify infrastructure state, execute commands, or cause side effects. While it operates within a Proxmox virtualization environment, the specific action (log retrieval) falls squarely into the Read category.

From the tool's definition Tool name includes 'logs' and description states 'Get Docker Swarm service logs' — a retrieval operation with no modification, execution, or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

proxmox_docker_service_logs Allowed

proxmox_docker_service_logs 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_service_logs": {}
  }
}

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

FAQ

Questions about proxmox_docker_service_logs

What does the proxmox_docker_service_logs tool do? +

Get Docker Swarm service logs. 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_service_logs? +

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

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

Can I rate-limit proxmox_docker_service_logs? +

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

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

proxmox_docker_service_logs 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

The MCP Attack Database →

Guides

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