Skip to content

Rule Reference

SEC604lintai-ai-securitygovernancehardeningstablejsonwarn

MCP config: git rebase auto-approve

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

Deterministic signal basis

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

SEC604 / MCP-AUTOAPPROVE-GIT-REBASE

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

Why It Matters

git rebase rewrites commit history. Auto-approving it removes review from shared history-rewrite authority.

Trigger Shape

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

How To Fix

Remove shared git rebase auto-approval and keep history rewriting under explicit user review.