lintai docs

Appearance

Rule Reference

SEC358lintai-ai-securityguidancequalitypreviewmarkdownwarn

Plugin agent: `mcpServers` in frontmatter

Plugin agent frontmatter sets `mcpServers`

Public lane
guidance
Category
quality
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

Advice-oriented guidance and maintainability review.

How to read this category

Contract, schema, or config correctness signal.

Activation Model

Preset Activation

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

guidancesidecar lane

Lifecycle

Preview Lifecycle Contract

State

preview

Promotion blocker

Plugin agent frontmatter can still include unsupported MCP server experiments, so the first release stays spec-guidance-only.

Promotion requirements

Needs corpus-backed precision review, external usefulness evidence, and completed stable checklist metadata.

Canonical note

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

Nearby Signals

Related Rules

SEC353Copilot instructions: exceeds 4000 charsGitHub Copilot instruction markdown exceeds the 4000-character guidance limitguidancequalitymarkdown
SEC354Copilot instructions: missing `applyTo`Path-specific GitHub Copilot instruction markdown is missing `applyTo` frontmatterguidancequalitymarkdown
SEC355AI markdown: wildcard tool grantAI-native markdown frontmatter grants wildcard tool accessguidancehardeningmarkdown
SEC356Plugin agent: `permissionMode` in frontmatterPlugin agent frontmatter sets `permissionMode`guidancequalitymarkdown
SEC357Plugin agent: `hooks` in frontmatterPlugin agent frontmatter sets `hooks`guidancequalitymarkdown
SEC359Cursor rule: `alwaysApply` typeCursor rule frontmatter `alwaysApply` must be booleanguidancequalitymarkdown

Why It Matters ​

SEC358 flags plugin agent markdown whose frontmatter sets mcpServers.

This is useful because:

  • plugin agent content should not silently become MCP client wiring
  • it separates agent behavior from server configuration and trust policy
  • it aligns with a cleaner review boundary for shared plugin artifacts

What Triggers ​

This rule applies only to plugin agent markdown surfaces and triggers on parsed frontmatter that contains the exact key:

  • mcpServers

Example that triggers:

yaml
---
mcpServers:
  demo:
    command: npx
---

Examples that stay clean:

  • plugin agents without mcpServers in frontmatter
  • fixture-like paths under tests/, fixtures/, examples/, or samples/
  • ordinary instructions and skills outside plugin-agent surfaces

False Positives ​

This rule now lives in the explicit guidance lane because some repos may still document unsupported MCP-server experiments inside agent files. The signal is meant as structural guidance for cleaner boundaries and easier review.

Remediation ​

Remove mcpServers from plugin agent frontmatter and define MCP servers in plugin or client configuration instead.