lintai docs

Appearance

Rule Reference

SEC421lintai-ai-securitypreviewmarkdownwarn

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

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

Provider
lintai-ai-security
Surface
markdown
Scope
per_file
Tier
preview
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 clone grants in shared allowed-tools policy.

Deterministic signal basis

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

Malicious corpus
skill-git-clone-allowed-tools
Benign corpus
skill-git-clone-allowed-tools-specific-safe
structured evidence required remediation reviewed
Canonical note

Structural preview rule; deterministic today, but the preview contract may still evolve.

Nearby Signals

Related Rules

SEC101HTML comment: dangerous instructionsHidden HTML comment contains dangerous agent instructionsmarkdownpreview
SEC102Markdown: remote execution instructionMarkdown contains remote download-and-execute instruction outside code blocksmarkdownpreview
SEC103HTML comment: remote execution instructionHidden HTML comment contains remote download-and-execute instructionmarkdownpreview
SEC104Markdown: base64 executable payloadMarkdown contains a base64-decoded executable payload outside code blocksmarkdownpreview
SEC105Markdown: parent-directory file accessMarkdown instructions reference parent-directory traversal for file accessmarkdownpreview
SEC313Shell example: remote content piped to shellFenced shell example pipes remote content directly into a shellmarkdownpreview

SEC421 / MD-GIT-CLONE-ALLOWED-TOOLS ​

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

Why It Matters ​

Blanket git clone authority turns arbitrary remote repository fetch into shared team policy. In AI-native instruction files, that makes broad code-ingestion behavior easier to normalize than a narrower 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 clone:*)

Clean Cases ​

These stay clean:

  • more specific reviewed commands such as Bash(git clone https://github.com/acme/demo.git)
  • frontmatter that does not grant git clone
  • fixture-like examples under test or fixture paths

Example Trigger ​

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

Safer Example ​

md
---
allowed-tools:
  - Bash(git clone https://github.com/acme/demo.git)
  - Read
---

How To Fix ​

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