lintai docs

Appearance

Rule Reference

SEC690lintai-ai-securitystablejsonwarn

MCP config: browser credential store access

MCP configuration command accesses browser credential or cookie stores

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 direct access to browser credential or cookie storage files.

Deterministic signal basis

JsonSignals command-plus-args analysis over ArtifactKind::McpConfig for browser profile paths such as Chrome or Firefox state directories paired with secret-store files like `Cookies`, `Login Data`, `logins.json`, `key4.db`, `Web Data`, or `Local State`.

Malicious corpus
mcp-command-local-data-theft
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 ​

Browser credential and cookie stores can contain active sessions, saved passwords, and identity material that should never be touched by a committed MCP launcher.

What Triggers ​

SEC690 matches committed MCP command paths that access browser profile directories together with secret-store files like Cookies, Login Data, logins.json, key4.db, Web Data, or Local State.

False Positives ​

Normal committed MCP tooling should not inspect browser credential databases. If a local diagnostic task really needs that data, it should be kept out of shared committed config.

Remediation ​

Remove browser credential and cookie store access from the committed MCP launch path and keep browser profile data outside shared automation.