lintai docs

Appearance

Rule Reference

SEC527lintai-ai-securitystablemarkdownwarn

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

AI-native markdown frontmatter grants `Bash(*)` wildcard access

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 exact `Bash(*)` grants that expose unconstrained shell execution as shared default policy.

Deterministic signal basis

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

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

SEC527 / MD-BASH-WILDCARD ​

SEC527 flags AI-native markdown frontmatter when allowed-tools or allowed_tools contains the exact wildcard token Bash(*).

Why It Matters ​

Bash(*) turns unconstrained shell execution into shared default policy. In skills and instruction files, that is usually much broader than the workflow needs and hard to justify in review.

Trigger Shape ​

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

Safer Example ​

md
---
allowed-tools:
  - Bash(git status:*)
---