Skip to content

Rule Reference

SEC389lintai-ai-securitygovernancehardeningpreviewmarkdownwarn

AI markdown: bare WebSearch tool grant

AI-native markdown frontmatter grants bare `WebSearch` tool access

Public lane
governance
Category
hardening
Provider
lintai-ai-security
Scope
per-file
Surface
markdown
Tier
preview
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 frontmatter for bare WebSearch grants that omit a reviewed search scope.

Deterministic signal basis

MarkdownSignals exact frontmatter token detection for bare `WebSearch` inside allowed-tools or allowed_tools.

Malicious corpus
skill-risky-frontmatter-tool-grants
Benign corpus
skill-reviewed-frontmatter-tool-grants-safe
structured evidence required remediation reviewed
Canonical note

Structural preview rule; deterministic today, but the preview contract may still evolve.

Nearby Signals

Related Rules

SEC389 / MD-WEBSEARCH-UNSCOPED

SEC389 flags AI-native markdown frontmatter when allowed-tools or allowed_tools grants bare WebSearch.

Why It Matters

Bare WebSearch is a broad capability grant. In shared skills or instruction files it is easy to cargo-cult into repositories without review, which makes network-search scope harder to reason about than an explicit constrained pattern.

Trigger Shape

The rule triggers only when all of these are true:

  • the file is a detected AI-native markdown instruction surface
  • the path is not fixture-like
  • allowed-tools or allowed_tools contains the exact token WebSearch

Clean Cases

These stay clean:

  • scoped patterns such as WebSearch(site:docs.example.com)
  • wildcard search grants, which should be handled separately if promoted later
  • fixture-like examples under test or fixture paths

Example Trigger

yaml
---
allowed-tools: WebSearch, Read
---

Safer Example

yaml
---
allowed-tools: WebSearch(site:docs.example.com), Read
---

How To Fix

Replace bare WebSearch with a narrower reviewed search pattern, or remove broad search access from the shared frontmatter grant.