lintai docs

Appearance

Rule Reference

SEC705lintai-ai-securitystablejsonwarn

MCP config: screen capture

MCP configuration command captures a screenshot or desktop image

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 screen capture utilities.

Deterministic signal basis

JsonSignals command-plus-args analysis over ArtifactKind::McpConfig for explicit screen capture utilities such as `screencapture`, `scrot`, `gnome-screenshot`, `grim`, `maim`, `grimshot`, ImageMagick `import -window root`, or PowerShell `CopyFromScreen`.

Malicious corpus
mcp-command-screen-capturemcp-command-screen-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 ​

A committed MCP launcher that captures the desktop can silently collect visible secrets and user activity from developer machines.

What Triggers ​

SEC705 matches committed MCP command paths that invoke explicit screen capture utilities such as screencapture, scrot, gnome-screenshot, grim, grimshot, maim, ImageMagick import -window root, or PowerShell CopyFromScreen.

False Positives ​

Committed MCP launchers should not capture screenshots from user machines. If a screen capture workflow is truly needed, it should be explicit and user-driven rather than hidden in shared committed config.

Remediation ​

Remove screenshot capture behavior from the committed MCP launch path and require deliberate user action outside shared automation.