Execute PowerShell commands and return the output with status code
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.
This tool directly executes arbitrary PowerShell commands, which can perform any action a user with the current process privileges can do, including installing malware, exfiltrating data, modifying system settings, or chaining to destructive operations. The blast radius is maximal—an agent with unconstrained access to this tool could compromise the entire Windows system.
From the tool's definition Tool description states 'Execute PowerShell commands and return the output with status code'. PowerShell is a command-line shell and scripting language that can run arbitrary code, system commands, and administrative operations on Windows systems.
Attacks that exploit this kind of access
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.
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.
Powershell-Tool 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 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.
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.
Powershell-Tool is provided by the Windows- MCP server (zhouke2020/cursortouch-windows-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →