lintai docs

Appearance

Rule Reference

SEC422lintai-ai-securitystablejsonwarn

MCP config: sudo command

MCP configuration launches the server through `sudo`

Provider
lintai-ai-security
Surface
json
Scope
per_file
Tier
stable
Severity
warn
Confidence
high
Detection
structural
Remediation
message_only

Activation Model

Preset Membership

This rule is part of the builtin activation graph through these preset memberships.

basemembership
mcpmembership

Lifecycle

Stable Lifecycle Contract

State

stable_gated

Graduation rationale

Matches exact MCP server launch paths that run under `sudo`.

Deterministic signal basis

JsonSignals exact string detection for `command: "sudo"` on parsed MCP configuration objects.

Malicious corpus
mcp-command-sudo
Benign corpus
mcp-command-non-sudo-safe
structured evidence required remediation reviewed
Canonical note

Structural stable rule intended as a high-precision check with deterministic evidence.

Nearby Signals

Related Rules

SEC301MCP config: shell trampolineMCP configuration shells out through sh -c or bash -cjsonstable
SEC302Config: insecure HTTP endpointConfiguration contains an insecure http:// endpointjsonstable
SEC303MCP config: credential env passthroughMCP configuration passes through credential environment variablesjsonstable
SEC304Config: TLS verification disabledConfiguration disables TLS or certificate verificationjsonstable
SEC305Config: hardcoded auth materialConfiguration embeds static authentication material in a connection or auth valuejsonstable
SEC309Config: literal secrets in configConfiguration commits literal secret material in env, auth, or header valuesjsonstable

SEC422 / MCP-COMMAND-SUDO ​

SEC422 flags MCP configuration when a committed server entry uses the exact launch command sudo.

Why It Matters ​

Running an MCP server through sudo bakes privilege escalation directly into shared client config. That is a high-confidence least-privilege smell and makes accidental elevated execution easier for every consumer of the config.

Trigger Shape ​

The rule triggers only when all of these are true:

  • the file is parsed as MCP configuration
  • a server entry contains command: "sudo"

Clean Cases ​

These stay clean:

  • ordinary non-privileged launch commands such as node, python, or uvx
  • MCP configs that do not route server launch through sudo

Example Trigger ​

json
{
  "mcpServers": {
    "demo": {
      "command": "sudo",
      "args": ["node", "server.js"]
    }
  }
}

Safer Example ​

json
{
  "mcpServers": {
    "demo": {
      "command": "node",
      "args": ["server.js"]
    }
  }
}

How To Fix ​

Remove sudo from the committed MCP launch path and use a reviewed non-privileged server command instead.