Skip to content

Rule Reference

SEC592lintai-ai-securitystablejsonwarn

MCP config: pipx run auto-approve

MCP configuration auto-approves `Bash(pipx run ...)` through `autoApprove`

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.

Lifecycle

Stable Lifecycle Contract

State

stable_gated

Graduation rationale

Matches exact `Bash(pipx run ...)` auto-approval in MCP client config.

Deterministic signal basis

JsonSignals exact array-item prefix detection for `autoApprove` entries starting with `Bash(pipx run ` on parsed MCP configuration.

Malicious corpus
mcp-autoapprove-mutable-runner-family
Benign corpus
mcp-autoapprove-mutable-runner-family-specific-safe
structured evidence required remediation reviewed
Canonical note

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

Nearby Signals

Related Rules

SEC592 / MCP-AUTOAPPROVE-PIPX-RUN

SEC592 flags MCP configuration when autoApprove includes a Bash(pipx run ...) tool token.

Why It Matters

pipx run enables mutable package execution from Python package sources. Auto-approving it removes review from dynamic package execution.

Trigger Shape

  • the file is a detected MCP configuration surface
  • autoApprove is a string array
  • the array contains an item starting with Bash(pipx run

How To Fix

Remove shared pipx run auto-approval and keep mutable package execution under explicit user review.