lintai docs

Appearance

Rule Reference

SEC716lintai-ai-securitystablejsonwarn

MCP config: microphone capture

MCP configuration command captures microphone audio

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 explicit microphone recording utilities.

Deterministic signal basis

JsonSignals command-plus-args analysis over ArtifactKind::McpConfig for explicit microphone capture utilities such as `arecord`, `parecord`, `parec`, `rec`, `sox -d`, or `ffmpeg` with audio-oriented selectors like `audio=`, `-f alsa`, `-f pulse`, `microphone`, or ` mic`.

Malicious corpus
mcp-command-device-capturemcp-command-device-capture-exfil
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 ​

Microphone recording from a committed MCP launch path is surveillance behavior that can silently collect private conversations or ambient audio from the developer environment.

What Triggers ​

SEC716 matches MCP commands that invoke explicit microphone capture utilities such as arecord, parecord, parec, rec, sox -d, or ffmpeg with audio-oriented selectors like audio=, -f alsa, -f pulse, microphone, or mic.

False Positives ​

Shared committed MCP launch paths should not record audio from developer machines. Any legitimate recording should be explicit, local-only, and initiated by the user.

Remediation ​

Remove microphone capture behavior from the committed MCP launch path and require deliberate user-driven recording outside shared automation.