Skip to content

Rule Reference

SEC675lintai-ai-securitythreat-reviewsecuritystablejsonwarn

MCP config: insecure HTTP secret send

MCP configuration command sends secret material to an insecure http:// endpoint

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 secret-bearing exfil over insecure HTTP.

Deterministic signal basis

JsonSignals command-plus-args analysis over ArtifactKind::McpConfig for `http://` endpoints gated by concurrent secret markers in a network-capable command path.

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

Sending secret material over plain HTTP exposes credentials to interception and makes an exfiltration path even easier to exploit.

What Triggers

SEC675 matches MCP launch commands where a secret-bearing network send targets an explicit http:// endpoint.

False Positives

Shared committed launch commands should not move secrets over plain HTTP. Local test fixtures without live credentials should stay out of committed production-facing MCP configs.

Remediation

Remove the insecure secret-bearing HTTP request or redesign the flow so secrets never leave the trusted process boundary.