Powershell-Tool · Windows- MCP: Risk & Policy

WHAT IT DOES

What Powershell-Tool does on Windows-MCP

AI agents invoke Powershell-Tool to trigger actions in Windows-MCP. 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 IT NEEDS A POLICY

Why Powershell-Tool needs a policy

This tool executes arbitrary PowerShell commands, which is a core example of the Execute category. PowerShell commands can perform virtually any action on a Windows system including reading/writing files, modifying system configuration, launching applications, accessing network resources, and potentially destructive operations.

From the tool's definition Tool name is 'Powershell-Tool' and description states it will 'Execute PowerShell commands and return the output with status code'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

Powershell-Tool Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "Powershell-Tool": {
      "limits": [
        {
          "counter": "powershell-tool_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Windows-MCP, so you can run agents against it safely.

FAQ

Questions about Powershell-Tool

What does the Powershell-Tool tool do? +

Execute PowerShell commands and return the output with status code. It is categorised as a Execute tool in the Windows-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on Powershell-Tool? +

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

What risk level is Powershell-Tool? +

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

Can I rate-limit Powershell-Tool? +

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

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

Powershell-Tool is provided by the Windows- MCP server (stepbystep-1/winows-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.