SCC MCP: Add organization-level findings support

[mm-pps]

Summary

The current SCC MCP server only supports project-level queries (projects/{project_id}/sources/-), but most SCC Enterprise customers manage findings at the organization level. There is no way to query findings across all projects in an organization without making individual calls per project.

Problem

In scc_mcp.py, the parent is hardcoded to project scope:

parent = f"projects/{project_id}/sources/-"

The SCC API natively supports organization-level queries using organizations/{org_id}/sources/- as the parent, but the MCP tools (top_vulnerability_findings, get_finding_remediation) don't expose an organization_id parameter.

Proposed Solution

Add an optional organization_id parameter to the SCC tools. When provided, use organizations/{organization_id}/sources/- as the parent instead of the project-scoped one. This would allow querying findings across all projects in the organization, which is the standard workflow for SCC Enterprise customers.

Example:

if organization_id:
    parent = f"organizations/{organization_id}/sources/-"
else:
    parent = f"projects/{project_id}/sources/-"

Use Case

• SOC teams using SCC Enterprise manage findings at the org level, not per-project
• Triage workflows need visibility across all projects
• Organization-level queries are the default in the SCC console UI

[mm-pps]

Opened PR #249 with an implementation for this. The change adds an optional organization_id parameter to both top_vulnerability_findings and get_finding_remediation.

Tested against a live SCC Enterprise environment — org-level queries work correctly, and existing project-level queries are unaffected.