Appearance
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
mcpServersin frontmatter - fixture-like paths under
tests/,fixtures/,examples/, orsamples/ - ordinary instructions and skills outside plugin-agent surfaces
False Positives
This rule stays Preview 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.