lintai docs

Appearance

Rule Reference

SEC466lintai-ai-securitystablemarkdownwarn

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

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

Deterministic signal basis

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

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

SEC466 / MD-RM-ALLOWED-TOOLS flags AI-native markdown frontmatter that grants blanket rm authority through allowed-tools.

Why this matters:

  • Bash(rm:*) gives destructive file-removal authority as a default shared capability
  • the grant is much broader than a reviewed cleanup workflow
  • shared instructions should prefer a narrow scoped command instead of open-ended deletion authority

Triggers:

yaml
allowed-tools: Bash(rm:*)

Does not trigger:

yaml
allowed-tools: Bash(rm ./tmp/output.txt)

Remediation:

  • replace Bash(rm:*) with a narrower reviewed cleanup command or remove the grant entirely