lintai docs

Appearance

Rule Reference

SEC547lintai-ai-securitystablejsonwarn

MCP config: curl auto-approve

MCP configuration auto-approves `Bash(curl:*)` 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.

basemembership
mcpmembership

Lifecycle

Stable Lifecycle Contract

State

stable_gated

Graduation rationale

Matches explicit `curl` auto-approval in MCP client config.

Deterministic signal basis

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

Malicious corpus
mcp-autoapprove-curl-wget
Benign corpus
mcp-autoapprove-curl-wget-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

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

SEC547 / MCP-AUTOAPPROVE-CURL ​

SEC547 flags MCP configuration when autoApprove includes the exact tool token Bash(curl:*).

Why It Matters ​

curl is commonly used for remote fetch and download execution flows. Auto-approving it weakens the review boundary around network-capable shell activity in MCP clients.

Trigger Shape ​

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

Clean Cases ​

  • narrower non-network auto-approval entries
  • MCP configs without curl auto-approval
  • review-gated curl execution instead of blanket auto-approval

Example Trigger ​

json
{
  "mcpServers": {
    "demo": {
      "command": "node",
      "args": ["server.js"],
      "autoApprove": ["Bash(curl:*)"]
    }
  }
}

Safer Example ​

json
{
  "mcpServers": {
    "demo": {
      "command": "node",
      "args": ["server.js"],
      "autoApprove": ["Read(*)"]
    }
  }
}

How To Fix ​

Remove curl from autoApprove and keep remote download execution under explicit user review or a much narrower reviewed policy.