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 can leave a mutating operation unclassified and unlabeled for DIFC.
MCP tools scanned: 89
CLI write commands scanned: 81
Guard-covered write tools (tools.rs): 128
Tools with explicit DIFC rules (tool_rules.rs): 130
New gaps found this run: 1
MCP Tool Classification Gaps (tools.rs)
These MCP tools perform write or mutating operations but are missing from WRITE_OPERATIONS or READ_WRITE_OPERATIONS in guards/github-guard/rust-guard/src/tools.rs:
Tool Name
Operation Type
Suggested Classification
Notes
assign_copilot_to_issue_with_intent
write
WRITE_OPERATIONS
Remote GitHub MCP tool that records Copilot assignment intent and may launch the assignment when is_suggestion=false; it is listed in the upstream README but absent from the local guard lists.
These MCP tools exist in the upstream server but have no explicit match arm in apply_tool_labels in guards/github-guard/rust-guard/src/labels/tool_rules.rs:
Tool Name
Data Scope
Suggested Labels
Risk
assign_copilot_to_issue_with_intent
repo-scoped
secrecy: S(repo), integrity: writer
Medium
Suggested fix for tool_rules.rs
Add assign_copilot_to_issue_with_intent to the existing repo-scoped write arm next to assign_copilot_to_issue and request_copilot_review:
This tool should inherit the same repo-visibility secrecy and writer integrity handling already applied to the neighboring Copilot write tools.
GitHub CLI-Only Gaps
No new CLI-only gaps were found in the inspected mutating command set. The current synthetic entries and lock/unlock write-pattern coverage accounted for the CLI operations reviewed in this run.
Stale Guard Entries (bonus)
No new stale guard entries were identified after excluding intentional synthetic/internal guard entries.
Summary
The GitHub guard does not fully cover 1 operation from the github-mcp-server and/or GitHub CLI. This can leave a mutating operation unclassified and unlabeled for DIFC.
MCP Tool Classification Gaps (tools.rs)
These MCP tools perform write or mutating operations but are missing from
WRITE_OPERATIONSorREAD_WRITE_OPERATIONSinguards/github-guard/rust-guard/src/tools.rs:assign_copilot_to_issue_with_intentWRITE_OPERATIONSis_suggestion=false; it is listed in the upstream README but absent from the local guard lists.Suggested fix for tools.rs
MCP Tool DIFC Labeling Gaps (tool_rules.rs)
These MCP tools exist in the upstream server but have no explicit match arm in
apply_tool_labelsinguards/github-guard/rust-guard/src/labels/tool_rules.rs:assign_copilot_to_issue_with_intentS(repo), integrity:writerSuggested fix for tool_rules.rs
Add
assign_copilot_to_issue_with_intentto the existing repo-scoped write arm next toassign_copilot_to_issueandrequest_copilot_review:This tool should inherit the same repo-visibility secrecy and writer integrity handling already applied to the neighboring Copilot write tools.
GitHub CLI-Only Gaps
No new CLI-only gaps were found in the inspected mutating command set. The current synthetic entries and lock/unlock write-pattern coverage accounted for the CLI operations reviewed in this run.
Stale Guard Entries (bonus)
No new stale guard entries were identified after excluding intentional synthetic/internal guard entries.
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.