Skip to content

feat(supabase-mcp-server): enable security scanning with mock_env#380

Merged
rdimitrov merged 1 commit intomainfrom
feat/supabase-mcp-mock-env
Feb 5, 2026
Merged

feat(supabase-mcp-server): enable security scanning with mock_env#380
rdimitrov merged 1 commit intomainfrom
feat/supabase-mcp-mock-env

Conversation

@JAORMX
Copy link
Collaborator

@JAORMX JAORMX commented Feb 5, 2026

Summary

  • Replace insecure_ignore: true with mock_env configuration for SUPABASE_ACCESS_TOKEN
  • Update allowed_issues format from old (tool/analyzer/category) to standard (code) format
  • This allows the security scanner to start the server and analyze its 29 database tools

Test plan

  • Verified scan works locally with mock env: scanner connects, discovers 29 tools
  • execute_sql tool correctly flagged with AITech-1.1 (false positive, in allowed_issues)
  • CI security scan should pass with the allowed_issues configuration

🤖 Generated with Claude Code

- Replace insecure_ignore with mock_env configuration for the
  SUPABASE_ACCESS_TOKEN environment variable
- Update allowed_issues format to use standard code-based format
  (AITech-1.1) instead of the old tool/analyzer/category format

This allows the security scanner to start the server and analyze its
database tools.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@github-actions
Copy link

github-actions bot commented Feb 5, 2026

🔒 MCP Security Scan Results

✅ supabase-mcp-server

  • Status: Passed
  • Tools scanned: 0
  • Result: No security issues detected

Summary: Scanned 1 MCP server(s), all passed security checks. ✅

@rdimitrov rdimitrov merged commit 97e3051 into main Feb 5, 2026
13 checks passed
@rdimitrov rdimitrov deleted the feat/supabase-mcp-mock-env branch February 5, 2026 12:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants