PowerShell ExecSAFE
MCP Server for executing PowerShell scripts
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Overview
MCP PowerShell Exec Server is a lightweight server that accepts PowerShell scripts as strings, executes them, and returns the output. Enabling AI assistants to understand and work with PowerShell.
Features
- Accepts PowerShell scripts via string input
- Executes scripts securely in an MCP Server environment
- Returns execution results in real-time
Installation
Clone the repository and set up the server:
git clone https://github.com/yourusername/mcp-powershell-exec.git cd mcp-powershell-exec
In Action
Watch the video to see MCP PowerShell Exec Server in action:
Usage
Integration with GitHub Copilot in VSCode Insiders
To use this MCP server with GitHub Copilot in VSCode Insiders, follow these steps:
- Install VSCode Insiders
- Download and install the latest version of VSCode Insiders
- Install GitHub Copilot Extension
- Open VSCode Insiders
- Go to the Extensions marketplace
- Search for and install "GitHub Copilot"
- Configure MCP Server
- Open .vscode/mcp.json
{
"servers": {
"powershell-integration": {
"command": "py", // Python executable
"args": [
"drive:/yourpath/server.py"
],
"env": {}
}
}
}Replace the path with the actual path to your server.py file.
- Enable Agent Mode
- Open Copilot chat in VSCode Insiders
- Click on "Copilot Edits"
- Choose "Agent mode"
- Click the refresh button in the chat input to load the available tools
System Requirements
- Python: Version 3.10 or higher (required for optimal performance)
- PowerShell: Version 5.1
License
This project is licensed under the MIT License - see the LICENSE file for detail
cc1be436bcc4OBSERVED · 2026-10-07Exposed tools (1)
0 read · 1 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
run_powershell | write | Runs PowerShell code and returns the output. |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
cc1be436bcc4full audit observations/trust-audit/mcp-server/dfinke__powershell-exec.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-07 | cc1be436bcc4 | SAFE | B | 89 | first audit |
Questions
What is the PowerShell Exec MCP server?
MCP Server for executing PowerShell scripts
What tools does PowerShell Exec expose?
1 in total: 0 read-only, 1 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is PowerShell Exec safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does PowerShell Exec need?
No credential environment variables were found in its source, so it appears to need none.
How current is this page?
The grade is for one exact copy of the source (cc1be436bcc4), read on 2026-10-07. The repository is watched and re-audited when it changes.