fix(mcp): remove --sarif flag as param for secret scanning tool

[sathvi-k]

Pull Request Submission Checklist

• Follows CONTRIBUTING guidelines
• Commit messages
  are release-note ready, emphasizing
  what was changed, not how.
• Includes detailed description of changes
• Contains risk assessment (Low | Medium | High)
• Highlights breaking API changes (if applicable)
• Links to automated tests covering new functionality
• Includes manual testing instructions (if necessary)
• Updates relevant GitBook documentation (PR link: ___)
• Includes product update to be announced in the next stable release notes

What does this PR do?

Removes --sarif as a flag option for calling the snyk_secret_scan tool. This is a bug fix, as having this param as an option was causing a bug when calling the tool.

This fix commit was added to the release-candidate branch, so adding it to the main branch as well in this PR.

Where should the reviewer start?

How should this be manually tested?

Build the studio mcp server in the cli, and call the snyk_secret_scan tool. You should get results from the scan. If you try calling the tool with the --sarif flag, it will result in an error because --sarif is not an option for a param that the tool can be called with.

What's the product update that needs to be communicated to CLI users?

N/A bug for MCP users, this fixes the secret scan tool

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[snyk-pr-review-bot]

PR Reviewer Guide 🔍

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

📚 Repository Context Analyzed This review considered 3 relevant code sections from 3 files (average relevance: 0.84) scripts/upgrade-snyk-go-dependencies.go (lines 1-135) package.json (lines 1-223) package-lock.json (lines 6-275)