Skip to content

Rule Reference

SEC569lintai-ai-securitystablejsonwarn

MCP config: Edit wildcard auto-approve

MCP configuration auto-approves `Edit(*)` through `autoApprove`

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.

Lifecycle

Stable Lifecycle Contract

State

stable_gated

Graduation rationale

Matches explicit `Edit(*)` auto-approval in MCP client config.

Deterministic signal basis

JsonSignals exact array-item detection for `autoApprove: ["Edit(*)"]` on parsed MCP configuration.

Malicious corpus
mcp-autoapprove-wildcard-tool-family
Benign corpus
mcp-autoapprove-wildcard-tool-family-specific-safe
structured evidence required remediation reviewed
Canonical note

Structural stable rule intended as a high-precision check with deterministic evidence.

Nearby Signals

Related Rules

SEC569 / MCP-AUTOAPPROVE-EDIT-WILDCARD

SEC569 flags MCP configuration when autoApprove includes the exact tool token Edit(*).

Why It Matters

Edit(*) grants unconstrained editing authority. Auto-approving it removes review from broad repository mutation flows.

Trigger Shape

  • the file is a detected MCP configuration surface
  • autoApprove is a string array
  • the array contains the exact item Edit(*)

How To Fix

Remove Edit(*) from autoApprove and replace it with narrower reviewed edit scopes where possible.