proxmox_windows_services
Manage Windows services (list, restart).
This record as markdown: /tools/bsahane-mcp-proxmox/proxmox-windows-services.md
What proxmox_windows_services does on MCP Proxmox Server
AI agents invoke proxmox_windows_services 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.
Why proxmox_windows_services is rated High
This tool executes service management commands on Windows systems. While listing services is a read operation, the ability to restart services constitutes code execution with external effects—restarting a service can disrupt dependent applications, cause downtime, or trigger cascading failures in infrastructure.
From the tool's definition Tool name includes 'manage' and description explicitly states 'restart' services on Windows systems. Restarting services triggers external operations with side effects that depend on which service is targeted.
Attacks that exploit this kind of access
The rule that runs proxmox_windows_services 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_windows_services, this is the rule to start with:
proxmox_windows_services 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.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Proxmox Server, apply this rule, and every proxmox_windows_services call is checked against it from then on.
Questions about proxmox_windows_services
Manage Windows services (list, restart). 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.
Register the MCP Proxmox Server MCP server in PolicyLayer and add a rule for proxmox_windows_services: 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.
proxmox_windows_services is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the proxmox_windows_services 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.
Set action: deny in the PolicyLayer policy for proxmox_windows_services. 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.
proxmox_windows_services 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.
More on MCP Proxmox Server, and thousands of servers like it.
Across the catalogue