Skip to content

Rule Reference

SEC539lintai-ai-securitygovernancehardeningstablemarkdownwarn

AI markdown: shared gh repo edit tool grant

AI-native markdown frontmatter grants `Bash(gh repo edit:*)` tool access

Public lane
governance
Category
hardening
Provider
lintai-ai-security
Scope
per-file
Surface
markdown
Tier
stable
Severity
warn
Confidence
high
Detection
structural
Remediation
message only
How to read this lane

Shared authority and workflow policy review.

How to read this category

Least-privilege, provenance, or operational hygiene signal.

Activation Model

Preset Activation

These presets explain where this rule appears in the product experience.

Lifecycle

Stable Lifecycle Contract

State

stable

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

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.