service_control

THE RISK

High Risk

Starting, stopping, or restarting Windows services can disable critical system functionality, interrupt user sessions, or break application dependencies. While not irreversibly destructive (services can be restarted), these actions have significant immediate operational impact and could disrupt system stability or availability if misapplied.

From the tool's definition Tool description explicitly states 'Control Windows service (start, stop, restart, enable, disable)' — these are operations that trigger external system services whose effects depend on which service is targeted and what action is performed.

Documented attack patterns abuse exactly the kind of access service_control gives an agent:

HOW TO CONTROL SERVICE_CONTROL

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Windows, and nothing reaches the server without passing your rules. This is the rule we recommend for service_control:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "service_control": {
      "limits": [
        {
          "counter": "service_control_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

Create a free account and register Mcp Windows — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

More Mcp Windows tools

Destructive clean_empty_directories Remove empty directories recursively Destructive drop_event Drop a scheduled event. Destructive drop_partition Drop a partition from a table. Destructive drop_role Drop a role (MySQL 8.0+). Destructive drop_stored_function Drop a stored function. Destructive drop_stored_procedure Drop a stored procedure. Destructive event_log_clear Clear a Windows Event Log (requires admin privileges) Destructive mysql_delete_data Delete data from a table.

All 441 Mcp Windows tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in Mcp Windows → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the service_control tool do? +

Control Windows service (start, stop, restart, enable, disable). It is categorised as a Execute tool in the Mcp Windows MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on service_control? +

Register the Mcp Windows MCP server in PolicyLayer and add a rule for service_control: 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 Windows. Nothing to install.

What risk level is service_control? +

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

Can I rate-limit service_control? +

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

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

service_control is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Windows tool call.

Deterministic rules across all 441 Mcp Windows tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN MCP WINDOWS →

Free to start. No card required.

441 Mcp Windows tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT SERVICE_CONTROL ON MCP WINDOWS DOES

// THE RISK

// HOW TO CONTROL SERVICE_CONTROL

// EXPLORE