Skip to content

Rule Reference

SEC605lintai-ai-securitygovernancehardeningstablejsonwarn

MCP config: git merge auto-approve

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

Deterministic signal basis

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

Malicious corpus
mcp-autoapprove-git-history-family
Benign corpus
mcp-autoapprove-git-history-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

SEC605 / MCP-AUTOAPPROVE-GIT-MERGE

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

Why It Matters

git merge mutates branch history and can introduce remote or local changes into the current branch. Auto-approving it removes review from shared history-mutation authority.

Trigger Shape

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

How To Fix

Remove shared git merge auto-approval and keep history mutation under explicit user review.