You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The GitHub guard does not fully cover 1 operation from the github-mcp-server and/or GitHub CLI. This may allow a write operation to bypass DIFC classification when invoked through the GitHub CLI surface.
MCP tools scanned: 118
CLI write commands scanned: 84
Guard-covered write tools (tools.rs): 120
Tools with explicit DIFC rules (tool_rules.rs): 193
New gaps found this run: 1
MCP Tool Classification Gaps (tools.rs)
None. The current 118-tool upstream GitHub MCP surface is covered by the existing explicit write/read-write sets plus the guard's prefix-based classification rules.
MCP Tool DIFC Labeling Gaps (tool_rules.rs)
None. Every current upstream GitHub MCP tool has an explicit apply_tool_labels rule.
GitHub CLI-Only Gaps
These write operations are reachable via the GitHub CLI but have no corresponding modeled guard entry today:
CLI Command
REST Endpoint
GitHub API Action
Risk
gh codespace stop
POST /user/codespaces/{codespace_name}/stop and POST /orgs/{org}/members/{user}/codespaces/{codespace_name}/stop
Stops a running codespace
Medium
Suggested remediation
Add a modeled CLI-only operation name such as stop_codespace to WRITE_OPERATIONS in guards/github-guard/rust-guard/src/tools.rs.
If this operation is later surfaced as an MCP tool or other first-class action, add an explicit apply_tool_labels arm in guards/github-guard/rust-guard/src/labels/tool_rules.rs that treats it as a private user/org-scoped write.
Consider filing an upstream github-mcp-server feature request for codespace lifecycle controls so the operation can be guarded through the MCP surface as well.
Summary
The GitHub guard does not fully cover 1 operation from the github-mcp-server and/or GitHub CLI. This may allow a write operation to bypass DIFC classification when invoked through the GitHub CLI surface.
MCP Tool Classification Gaps (tools.rs)
None. The current 118-tool upstream GitHub MCP surface is covered by the existing explicit write/read-write sets plus the guard's prefix-based classification rules.
MCP Tool DIFC Labeling Gaps (tool_rules.rs)
None. Every current upstream GitHub MCP tool has an explicit
apply_tool_labelsrule.GitHub CLI-Only Gaps
These write operations are reachable via the GitHub CLI but have no corresponding modeled guard entry today:
gh codespace stopPOST /user/codespaces/{codespace_name}/stopandPOST /orgs/{org}/members/{user}/codespaces/{codespace_name}/stopSuggested remediation
stop_codespacetoWRITE_OPERATIONSinguards/github-guard/rust-guard/src/tools.rs.apply_tool_labelsarm inguards/github-guard/rust-guard/src/labels/tool_rules.rsthat treats it as a private user/org-scoped write.Suggested fix for tools.rs
Stale Guard Entries (bonus)
None identified in this run.
References
Warning
Firewall blocked 2 domains
The following domains were blocked by the firewall during workflow execution:
awmgmcpgproxy.golang.orgSee Network Configuration for more information.