Skip to content

Rule Reference

SEC568lintai-ai-securitystablejsonwarn

MCP config: Write wildcard auto-approve

MCP configuration auto-approves `Write(*)` 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 `Write(*)` auto-approval in MCP client config.

Deterministic signal basis

JsonSignals exact array-item detection for `autoApprove: ["Write(*)"]` 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

SEC568 / MCP-AUTOAPPROVE-WRITE-WILDCARD

SEC568 flags MCP configuration when autoApprove includes the exact tool token Write(*).

Why It Matters

Write(*) grants unconstrained file mutation. Auto-approving it removes review from broad write authority in shared MCP client policy.

Trigger Shape

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

How To Fix

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