lintai docs

Appearance

Rule Reference

SEC539lintai-ai-securitystablemarkdownwarn

AI markdown: shared gh repo edit tool grant

AI-native markdown frontmatter grants `Bash(gh repo edit:*)` tool 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.

governancemembership

Lifecycle

Stable Lifecycle Contract

State

stable_gated

Graduation rationale

Checks AI-native markdown frontmatter for exact GitHub repository settings mutation authority through `allowed-tools`.

Deterministic signal basis

MarkdownSignals exact frontmatter string detection for `Bash(gh repo edit:*)` in allowed-tools entries.

Malicious corpus
skill-gh-repo-edit-release-create-allowed-tools
Benign corpus
skill-gh-repo-edit-release-create-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

SEC423AI markdown: bare Read tool grantAI-native markdown frontmatter grants bare `Read` tool accessmarkdownstable
SEC424AI markdown: bare Write tool grantAI-native markdown frontmatter grants bare `Write` tool accessmarkdownstable
SEC425AI markdown: bare Edit tool grantAI-native markdown frontmatter grants bare `Edit` tool accessmarkdownstable
SEC426AI markdown: bare Glob tool grantAI-native markdown frontmatter grants bare `Glob` tool accessmarkdownstable
SEC427AI markdown: bare Grep tool grantAI-native markdown frontmatter grants bare `Grep` tool accessmarkdownstable
SEC505AI markdown: shared gh api POST tool grantAI-native markdown frontmatter grants `Bash(gh api --method POST:*)` tool accessmarkdownstable

SEC539 / MD-GH-REPO-EDIT-ALLOWED-TOOLS ​

SEC539 flags AI-native markdown frontmatter when allowed-tools grants blanket gh repo edit authority.

Why It Matters ​

gh repo edit can mutate repository settings. In shared AI-native markdown guidance that is broader than most teams want to advertise as default agent authority.

Trigger Shape ​

  • the file is an AI-native markdown surface
  • the path is not fixture-like
  • frontmatter allowed-tools or allowed_tools contains the exact token Bash(gh repo edit:*)

Clean Cases ​

  • narrower read-only grants such as Bash(gh repo view:*)
  • markdown surfaces without blanket repository edit grants
  • fixture-like examples under test or fixture paths

Example Trigger ​

yaml
---
allowed-tools:
  - Bash(gh repo edit:*)
---

Safer Example ​

yaml
---
allowed-tools:
  - Bash(gh repo view:*)
---

How To Fix ​

Remove shared gh repo edit tool grants or replace them with narrower reviewed commands that keep repository settings mutation under explicit user control.