Skip to content

Rule Reference

SEC594lintai-ai-securitygovernancehardeningstablejsonwarn

MCP config: git clone auto-approve

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

Deterministic signal basis

JsonSignals exact array-item detection for `autoApprove: ["Bash(git clone:*)"]` 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

SEC594 / MCP-AUTOAPPROVE-GIT-CLONE

SEC594 flags MCP configuration when autoApprove includes the exact tool token Bash(git clone:*).

Why It Matters

git clone fetches remote repository content. Auto-approving it removes review from shared repository fetch authority.

Trigger Shape

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

How To Fix

Remove shared git clone auto-approval and keep repository fetches under explicit user review.