microsoft/azure-skills microsoft-foundry
Checked the catalogued skill at microsoft-foundry.
D; retained sample includes a high finding · SD-007 · what this rule accepts as a false positive →
F; retained sample includes a high finding · SD-003 · what this rule accepts as a false positive →
B set by findings not listed in the stored summary
19 suppressed by AI triage
The flagged text is a documentation warning, not an actual path traversal path or code.
The detected path traversal appears only in a Markdown link pointing to another documentation file, which is non-executable and harmless.
The '../' sequence appears only in a Markdown link to documentation, a normal relative path in prose, not an executable path traversal.
The text is documentation and does not contain any real path traversal or absolute path usage.
The file contains documentation, not code, and only references a detected outbound call in text, not an actual network operation.
The '..' appears only in a relative documentation link, not in executable code or file system paths.
Documentation only refers to path traversal concepts, not executing any traversal code.
No actual path traversal strings are present in the file content.
The file contains only blank lines; no actual path traversal or absolute path is present.
The file is a documentation prose that only describes DNS exfiltration concepts, not an actual implementation.
The relative link to ../toolbox.md is just a documentation reference, not an executable path traversal.
The flagged content is generic documentation; no actual path traversal code or file operations are present
Documentation file; no executable path traversal found.
The file is a documentation text with no executable code or config that would enable outbound network calls.
The file contains documentation, not code, and only references a detected outbound call in text, not an actual network operation.
The flagged line is documentation, not executable code, so it poses no real threat.
Documentation config example, not an active outbound call.
The manifest contains no actual path traversal or system directory references, likely a false positive detection.
Placeholder reference in prose, no real path traversal.