Skip to content

Rule Reference

SEC596lintai-ai-securitygovernancehardeningstablejsonwarn

MCP config: git ls-remote auto-approve

MCP configuration auto-approves `Bash(git ls-remote:*)` 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(git ls-remote:*)` auto-approval in MCP client config.

Deterministic signal basis

JsonSignals exact array-item detection for `autoApprove: ["Bash(git ls-remote:*)"]` on parsed MCP configuration.

Malicious corpus
mcp-autoapprove-repo-fetch-family
Benign corpus
mcp-autoapprove-repo-fetch-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

SEC596 / MCP-AUTOAPPROVE-GIT-LS-REMOTE

SEC596 flags MCP configuration when autoApprove includes the exact tool token Bash(git ls-remote:*).

Why It Matters

git ls-remote reaches out to remote repositories and exposes remote metadata. Auto-approving it removes review from shared remote-inspection authority.

Trigger Shape

  • the file is a detected MCP configuration surface
  • autoApprove is a string array
  • the array contains the exact item Bash(git ls-remote:*)

How To Fix

Remove shared git ls-remote auto-approval and keep remote repository inspection under explicit user review.