lintai docs

Appearance

Rule Reference

SEC433lintai-ai-securitystablemarkdownwarn

AI markdown: `Bash(git fetch:*)` tool grant

AI-native markdown frontmatter grants `Bash(git fetch:*)` authority

Provider
lintai-ai-security
Surface
markdown
Scope
per_file
Tier
stable
Severity
warn
Confidence
high
Detection
structural
Remediation
message_only

Activation Model

Preset Membership

This rule is part of the builtin activation graph through these preset memberships.

previewmembership
skillsmembership

Lifecycle

Stable Lifecycle Contract

State

stable_gated

Graduation rationale

Checks AI-native frontmatter for wildcard git fetch grants in shared allowed-tools policy.

Deterministic signal basis

MarkdownSignals exact frontmatter token detection for `Bash(git fetch:*)` inside allowed-tools or allowed_tools.

Malicious corpus
skill-git-fetch-allowed-tools
Benign corpus
skill-git-fetch-allowed-tools-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

SEC352AI markdown: unscoped Bash tool grantAI-native markdown frontmatter grants unscoped Bash tool accessmarkdownstable
SEC417AI markdown: unpinned pip git installAI-native markdown installs Python packages from an unpinned `git+https://` sourcemarkdownstable
SEC428AI markdown: unsafe Read path grantAI-native markdown frontmatter grants `Read(...)` over an unsafe repo-external pathmarkdownstable
SEC429AI markdown: unsafe Write path grantAI-native markdown frontmatter grants `Write(...)` over an unsafe repo-external pathmarkdownstable
SEC430AI markdown: unsafe Edit path grantAI-native markdown frontmatter grants `Edit(...)` over an unsafe repo-external pathmarkdownstable
SEC431AI markdown: unsafe Glob path grantAI-native markdown frontmatter grants `Glob(...)` over an unsafe repo-external pathmarkdownstable

SEC433 / MD-GIT-FETCH-ALLOWED-TOOLS ​

SEC433 flags AI-native markdown frontmatter when allowed-tools grants the exact token Bash(git fetch:*).

Why It Matters ​

Blanket git fetch authority normalizes remote repository synchronization as default team policy. In shared AI instructions, that broadens network-driven code ingestion beyond a narrowly reviewed fetch workflow.

Trigger Shape ​

The rule triggers only when all of these are true:

  • the file is an AI-native markdown instruction surface with parsed frontmatter
  • the path is not fixture-like
  • allowed-tools or allowed_tools contains the exact token Bash(git fetch:*)

Clean Cases ​

These stay clean:

  • more specific reviewed commands such as Bash(git fetch origin main)
  • frontmatter that does not grant git fetch
  • fixture-like examples under test or fixture paths

Example Trigger ​

md
---
allowed-tools:
  - Bash(git fetch:*)
  - Read
---

Safer Example ​

md
---
allowed-tools:
  - Bash(git fetch origin main)
  - Read
---

How To Fix ​

Replace Bash(git fetch:*) with a narrower reviewed command pattern, or remove broad fetch authority from shared frontmatter entirely.