Skip to content

Rule Reference

SEC674lintai-ai-securitythreat-reviewsecuritystablejsonwarn

MCP config: secret exfiltration

MCP configuration command appears to send secret material over the network

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

Explicit malicious, secret-bearing, or spyware-like review.

How to read this category

Strong exploit, secret, or unsafe-execution 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 committed MCP launch paths for explicit secret-bearing network exfil payloads.

Deterministic signal basis

JsonSignals command-plus-args analysis over ArtifactKind::McpConfig for secret markers combined with network-capable command context.

Malicious corpus
mcp-command-secret-exfil-payloads
Benign corpus
mcp-safe-basic
structured evidence required remediation reviewed
Canonical note

Structural stable rule positioned as an explicit threat-review control: high-signal malicious, credential-bearing, or spyware-like behavior that stays opt-in rather than shaping the quiet default.

Nearby Signals

Related Rules

Why It Matters

Committed MCP launch commands should not forward credentials or secret tokens to remote endpoints as part of their normal startup path.

What Triggers

SEC674 matches MCP command and args combinations that mix secret markers such as OPENAI_API_KEY, AWS_SECRET_ACCESS_KEY, bearer auth, or cookie material with a network-capable command path.

False Positives

This rule is intentionally narrow to committed launch commands. If a server legitimately uses auth to talk to its own backend, move that logic inside the server process rather than baking secret sends into the shared launcher.

Remediation

Remove the secret-bearing network send from the committed MCP launch path and keep secret handling inside the target service or provider-local configuration.