Appearance
Why It Matters
Dumping environment variables from a committed MCP launch path is high-risk because developer shells often contain tokens, API keys, cloud credentials, and session material.
What Triggers
SEC737 matches MCP commands that invoke explicit environment enumeration primitives such as printenv, env used as a dump, export -p, declare -xp, or compgen -v.
False Positives
Shared committed MCP launch paths should not enumerate the developer environment. Legitimate diagnostics should be explicit, local-only, and initiated by the user.
Remediation
Remove environment dumping behavior from the committed MCP launch path and require deliberate user-driven diagnostics outside shared automation.