Skip to content

Rule Reference

SEC729lintai-ai-securitythreat-reviewsecuritystablejsonwarn

MCP config: keylogger capture

MCP configuration command captures keystrokes or keyboard input

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 keystroke capture utilities or keylogger markers.

Deterministic signal basis

JsonSignals command-plus-args analysis over ArtifactKind::McpConfig for explicit keylogger primitives such as `logkeys`, `xinput test`, `evtest`, `showkey`, PowerShell `GetAsyncKeyState`, or inline Python listener markers like `pynput.keyboard.Listener`.

Malicious corpus
mcp-command-keyloggermcp-command-keylogger-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

Keylogging from a committed MCP launch path is spyware behavior because it can silently capture secrets, credentials, prompts, and private communications typed by the developer.

What Triggers

SEC729 matches MCP commands that invoke explicit keylogger primitives such as logkeys, xinput test, evtest, showkey, PowerShell GetAsyncKeyState, or inline Python listener markers like pynput.keyboard.Listener.

False Positives

Shared committed MCP launch paths should not capture keyboard input. Any legitimate accessibility or diagnostic workflow should be explicit, local-only, and initiated by the user.

Remediation

Remove keystroke capture or keylogger behavior from the committed MCP launch path and require deliberate user-driven diagnostics outside shared automation.