lintai docs

Appearance

Rule Reference

SEC729lintai-ai-securitystablejsonwarn

MCP config: keylogger capture

MCP configuration command captures keystrokes or keyboard input

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

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.