proxmox_windows_services

Manage Windows services (list, restart).

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-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.

Questions about proxmox_windows_services

What does the proxmox_windows_services tool do? +

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.

How do I enforce a policy on proxmox_windows_services? +

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.

What risk level is proxmox_windows_services? +

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

Can I rate-limit proxmox_windows_services? +

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.

How do I block proxmox_windows_services completely? +

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.

What MCP server provides proxmox_windows_services? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of MCP Proxmox Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.