Is Codescene MCP server safe?
- Node.js shell/command execution
- Possible command injection (exec with dynamic command)
- MCP server launches a host command
repo is an AI ai_component analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators, though 5 risky constructs are reported for review. It can: mcp tools detected, network egress and shell execution — capabilities are what the code can do, not a verdict on intent. Risk score 20/100 (low).
repo
Automated static-analysis result. It can contain false positives and false negatives, and is not a claim about the intent of Codescene MCP server's authors. Report a false positive.
Behavioral traits
How this component maps to the CSA agentic threat model. Descriptive — it never affects the risk score.
Findings (5)
The code builds an OS command out of values that can change at runtime, then runs it through a shell.
execSync(`node scripts/download-binary.js ${binaryTarget}`, {execSync(`npx @vscode/vsce package --target ${vsTarget}`, {Why it matters: If any of those values come from untrusted input, an attacker can run their own commands on the machine.
Fix: Use execFile/spawn with an argument array instead of exec; never build a shell command string from external input.
An MCP server entry launches a command on your host.
"command": "npx",
Why it matters: Trusting the manifest means running that binary — verify what it is and where it comes from.
Fix: Verify the launched command and its source before trusting this MCP server configuration.
The component can run operating-system commands or spawn processes.
import { execFileSync } from "node:child_process";import { spawn } from "node:child_process";const child = spawn(binaryPath, args, {import { execFileSync } from 'node:child_process';import { execSync } from 'node:child_process';execSync(`node scripts/download-binary.js ${binaryTarget}`, {execSync(`npx @vscode/vsce package --target ${vsTarget}`, {import { execFile } from 'child_process';Why it matters: Powerful and often legitimate — confirm the commands aren't built from untrusted input.
Fix: Confirm the command and its arguments are fully controlled and not derived from untrusted input; prefer execFile with an argument array.
The component makes outbound network requests.
import https from "node:https";
import http from "node:http";
import https from 'node:https';
import http from 'node:http';
Why it matters: Usually legitimate, but confirm the destinations are expected and no sensitive data leaves.
Fix: Confirm the destination hosts are expected and that no sensitive data is sent off-host.
An MCP tool surface (manifest or tool definitions) was found.
"mcpServers": {Why it matters: Just context — review which tools it offers and their permissions.
Fix: Review the declared MCP tools and their permissions.
Check your own component
Run the same evidence-backed scan on any MCP server, agent skill, or package.
Scan your own componentHow we determine this: deterministic static analysis (regex + AST), evidence-anchored, no code execution. Methodology →