Skip to content

Rule Reference

SEC715lintai-ai-securitythreat-reviewsecuritystablejsonwarn

MCP config: camera capture

MCP configuration command captures a webcam or camera image

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 explicit webcam or camera capture utilities.

Deterministic signal basis

JsonSignals command-plus-args analysis over ArtifactKind::McpConfig for explicit camera capture utilities such as `imagesnap`, `fswebcam`, or `ffmpeg` with camera-oriented selectors like `video=`, `/dev/video`, `-f v4l2`, `-f video4linux2`, `webcam`, or `camera`.

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 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

Camera capture from a committed MCP launch path is spyware-like behavior because it can silently collect sensitive imagery from the developer environment.

What Triggers

SEC715 matches MCP commands that invoke explicit camera capture utilities such as imagesnap, fswebcam, or ffmpeg with camera-oriented selectors like video=, /dev/video, -f v4l2, -f video4linux2, webcam, or camera.

False Positives

Shared committed MCP launch paths should not activate a developer's camera. Any legitimate capture should be explicit, local-only, and initiated by the user.

Remediation

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