lintai docs

Appearance

Rule Reference

SEC302lintai-ai-securitystablejsonwarn

Config: insecure HTTP endpoint

Configuration contains an insecure http:// endpoint

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

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

Matches explicit insecure http:// endpoints in configuration values.

Deterministic signal basis

JsonSignals precise http:// endpoint span resolution from parsed JSON location map.

Malicious corpus
mcp-plain-http
Benign corpus
mcp-trusted-endpoint-safe
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
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
SEC310Config: metadata or private-network hostConfiguration endpoint targets a metadata or private-network host literaljsonstable

Why It Matters ​

Committed config that points to http:// endpoints weakens transport integrity and confidentiality. For MCP and related config artifacts, that usually means the client is opting into a non-verified remote transport where HTTPS or local stdio would be safer.

What Triggers ​

SEC302 applies to parsed JSON configuration values and triggers on explicit insecure http:// endpoint literals.

Example that triggers:

json
{"url":"http://internal.test"}

Example that stays clean:

json
{"url":"https://internal.test"}

False Positives ​

This is a structural endpoint rule, not a prose heuristic. It reports the concrete http:// span from parsed JSON values and ignores non-endpoint text.

Remediation ​

Replace the insecure endpoint with HTTPS or a local stdio transport. When the finding is a direct http:// literal, the built-in suggestion can rewrite the prefix to https://.