[aw] Detection Runs
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 10/100
Research direction
This is an automatically managed detection-runs tracker, not an implementation task. Read the issue body and its workflow comments to understand the reported detection events; there is no code change to make, and the issue explicitly says not to assign or act on it.
Written by the indexing model from the issue text.
Description
This issue tracks all runs where threat detection flagged problems in agentic workflows in this repository. Each workflow run that completes with a detection warning or failure posts a comment here.
What is a Detection Problem?
A detection problem occurs when the threat detection system either:
- Detects potential security threats (prompt injection, secret leak, malicious patch)
- Fails to produce results (agent failure, parse error)
When continue-on-error: true (the default), these problems produce warnings and safe outputs still proceed. When continue-on-error: false, they block safe outputs entirely.
How This Helps
This issue helps you:
- Track workflows where threat detection raised concerns
- Review patterns of detection warnings or failures
- Identify false positives or recurring issues with threat detection
- Monitor the health of the threat detection system
Resources
[!TIP]
To configure threat detection behavior, update the frontmatter:safe-outputs: threat-detection: continue-on-error: true # Warnings only (default) # continue-on-error: false # Strict mode — block safe outputs
This issue is automatically managed by GitHub Agentic Workflows. Do not close this issue manually.
No action to take - Do not assign to an agent.
- expires on Oct 24, 2026, 6:11 AM UTC
- Dominant language
- C#
- Stars
- 3.7k
- Forks
- 627
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 190
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/mcp
-
copilot documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days
-
dependencies needs-team-triage server-Azure.Mcp
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microsoft/mcp#3752 · 1 comment ·
Maintainers usually reply within 2 days
-
Azure.Mcp.Server customer-reported needs-team-triage question server-Azure.Mcp tools-Deploy
Difficulty 3/5 1-2 days Newbie friendliness 35/100
microsoft/mcp#3813 · 1 comment ·
Maintainers usually reply within 2 days
-
Blocking upstream merge conflict: Azure.Mcp.Server-3.0.0-beta.48Possibly taken @g2vinay claimed this today. Opencustomer-reported needs-team-attention question server-Azure.Mcp tools-Core
microsoft/mcp#3812 · 1 comment · 1 assignee ·
Maintainers usually reply within 2 days
-
agentic-workflows
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 2 days
Similar issues
-
Money ExploitsOpenS: Untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
project-wayfarer/wayfarer-14#1628 ·
Maintainers usually reply within 3 days
-
:watch: Not Triaged dotnet-target-version
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
dotnet/dotnet-api-docs#13124 ·
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
microsoft/PowerPlatformConnectors#4320 ·
Maintainers usually reply within 4 days