Skip to content

Rule Reference

SEC589lintai-ai-securitygovernancehardeningstablejsonwarn

MCP config: bunx auto-approve

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

Public lane
governance
Category
hardening
Provider
lintai-ai-security
Scope
per-file
Surface
json
Tier
stable
Severity
warn
Confidence
high
Detection
structural
Remediation
message only
How to read this lane

Shared authority and workflow policy review.

How to read this category

Least-privilege, provenance, or operational hygiene signal.

Activation Model

Preset Activation

These presets explain where this rule appears in the product experience.

Lifecycle

Stable Lifecycle Contract

State

stable

Graduation rationale

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

Deterministic signal basis

JsonSignals exact array-item prefix detection for `autoApprove` entries starting with `Bash(bunx ` 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

SEC589 / MCP-AUTOAPPROVE-BUNX

SEC589 flags MCP configuration when autoApprove includes a Bash(bunx ...) tool token.

Why It Matters

bunx runs packages from a mutable package source. 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(bunx

How To Fix

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