High Risk →

windows_feature_control

Enable or disable Windows optional features

How to control windows_feature_control ↓

AI agents invoke windows_feature_control to trigger actions in Mcp Windows. 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.

High Risk

This tool modifies the Windows feature set by enabling or disabling optional OS components (e.g., Hyper-V, WSL, IIS). These are system-level configuration changes that trigger OS operations and can significantly alter system behavior, attack surface, and capabilities.

From the tool's definition Enable or disable Windows optional features

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

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 windows_feature_control:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "windows_feature_control": {
      "limits": [
        {
          "counter": "windows_feature_control_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Mcp Windows — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the windows_feature_control tool do? +

Enable or disable Windows optional features. 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 windows_feature_control? +

Register the Mcp Windows MCP server in PolicyLayer and add a rule for windows_feature_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 windows_feature_control? +

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

Can I rate-limit windows_feature_control? +

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

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

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

Free to start. No card required.

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

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.