Atlas / MCP servers / dfinke / PowerShell Exec

PowerShell ExecSAFE

mcp/dfinke/powershell-exec

MCP Server for executing PowerShell scripts

Verdict
SAFE
Grade
B
Trust score
89 /100
Exposed tools
1 0r · 1w · 0d
Transport
—
License
MIT
Stars
59
01

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:

  1. Install VSCode Insiders
  2. Download and install the latest version of VSCode Insiders
  1. Install GitHub Copilot Extension
  2. Open VSCode Insiders
  3. Go to the Extensions marketplace
  4. Search for and install "GitHub Copilot"
  1. Configure MCP Server
  2. 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.

  1. Enable Agent Mode
  2. Open Copilot chat in VSCode Insiders
  3. Click on "Copilot Edits"
  4. Choose "Agent mode"
  5. 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

Read from source at commit cc1be436bcc4OBSERVED · 2026-10-07
02

Exposed tools (1)

0 read · 1 write · 0 destructive.

ToolRiskDescription
run_powershellwriteRuns PowerShell code and returns the output.
03

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.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (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.

Audited 2026-10-07 · audit v0.4.1 · source sha cc1be436bcc4full audit observations/trust-audit/mcp-server/dfinke__powershell-exec.json · Report an issue / request a re-scan
04

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-07cc1be436bcc4SAFEB89first audit
05

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.

Advertisement