confirm_command
Confirm dangerous command execution
LABSCO SUMMARY
Execution and the check before it are separate calls, so the destructive path takes two.
The read tools cover exactly what you would look at before running anything — system information, environment, processes, disk usage, directory contents — and execute_command's own description points the caller at them first. Dangerous execution routes through confirm_command with a confirmation_id and an explicit confirm, so a badly worded single call does not reach the shell. What does run, runs with whatever the WSL session already has; the gate governs the second call, not the permissions.
What it is
A WSL command surface with the inspection tools on one side, execute_command on the other, and a confirmation step in between for anything dangerous.
What you get
- WSL system information, and the environment variables with an optional filter
- Running processes, filterable, and disk space for a given path
- Directory contents, with a details view when the listing alone is not enough
- Commands executed inside WSL with a working_dir and a timeout
- A confirmation gate — confirm_command takes a confirmation_id and an explicit confirm before a dangerous command execution goes ahead
Requirements
A WSL distribution on the host for the tools to read and run inside. Nothing is configured — no account, no key.
Setup effort
One command — npx -y mcp-wsl-exec
USE CASES
01
Working out what state the box is in before touching it
Pull the system information, read the environment the commands would inherit, and see what is already running.
02
Chasing a disk that filled up overnight
Check the space on the path that matters, then walk the directory with details on to find what grew.
03
Running something that deserves a second look first
Issue the command with its working directory and timeout; when it comes back flagged as dangerous, confirm it by id rather than by rephrasing.
7 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
execute_command
Execute a command in WSL (use read-only tools when possible)
get_directory_info
Get directory contents and info
get_disk_usage
Get disk space information
get_environment
Get WSL environment variables
get_system_info
Get WSL system information
list_processes
List running processes in WSL
BEFORE YOU INSTALL
What to know first
Tools you get
7 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 7 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-wsl-exec": {
"command": "npx",
"args": [
"-y",
"mcp-wsl-exec"
]
}
}
}npx
TERMINAL
npx -y mcp-wsl-exec
