lintai docs

Appearance

Rule Reference

SEC675lintai-ai-securitystablejsonwarn

MCP config: insecure HTTP secret send

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

Provider
lintai-ai-security
Surface
json
Scope
per_file
Tier
stable
Severity
warn
Confidence
high
Detection
structural
Remediation
message_only

Activation Model

Preset Membership

This rule is part of the builtin activation graph through these preset memberships.

basemembership
mcpmembership

Lifecycle

Stable Lifecycle Contract

State

stable_gated

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 intended as a high-precision check with deterministic evidence.

Nearby Signals

Related Rules

SEC301MCP config: shell trampolineMCP configuration shells out through sh -c or bash -cjsonstable
SEC302Config: insecure HTTP endpointConfiguration contains an insecure http:// endpointjsonstable
SEC303MCP config: credential env passthroughMCP configuration passes through credential environment variablesjsonstable
SEC304Config: TLS verification disabledConfiguration disables TLS or certificate verificationjsonstable
SEC305Config: hardcoded auth materialConfiguration embeds static authentication material in a connection or auth valuejsonstable
SEC309Config: literal secrets in configConfiguration commits literal secret material in env, auth, or header valuesjsonstable

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.