lintai docs

Appearance

Rule Reference

SEC470lintai-ai-securitystablemarkdownwarn

AI markdown: `Bash(su:*)` tool grant

AI-native markdown frontmatter grants `Bash(su:*)` 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 explicit wildcard su grants in shared allowed-tools policy.

Deterministic signal basis

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

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

SEC470 / MD-SU-ALLOWED-TOOLS flags AI-native markdown frontmatter that grants blanket su authority through allowed-tools.

Why this matters:

  • Bash(su:*) gives broad privilege-switch authority as a default shared capability
  • the grant is wider than a reviewed privilege-switch workflow
  • shared instructions should prefer a narrow scoped command instead of open-ended user switching

Triggers:

yaml
allowed-tools: Bash(su:*)

Does not trigger:

yaml
allowed-tools: Bash(su deploy)

Remediation:

  • replace Bash(su:*) with a narrower reviewed privilege-switch command or remove the grant entirely