TL;DR: Hidden HTML comments in Azure DevOps can steer an AI agent into cross-project actions it would not take alone, according to Manifold Security. Delegated authority now needs content boundaries and scoped execution checks, or attacker-writable text can redirect reviewer credentials into data theft.
Editorial analysis by NHI Mgmt Group, based on content published by Manifold Security: “When Your AI Reviewer Works for the Attacker: A Confused-Deputy Bug in Microsoft's Azure DevOps MCP Server”.
Key questions
Q: Why do AI agents create more risk than ordinary automation in pull request workflows?
A: Because an agent does not just execute a fixed script.
Q: What are the signs that prompt injection is reaching an AI agent through developer workflows?
A: Look for tool calls that do not match the user’s apparent request, especially when a review task leads to pipeline execution, wiki reads, or cross-project access.
Q: What breaks when an AI agent reads attacker-controlled PR text and can act on it?
A: The control that breaks is the assumption that review content is passive.
Practitioner guidance
- Map agent read and write paths Inventory every place an AI agent can consume attacker-writable content and then invoke a privileged tool, especially PRs, issues, comments, and wiki pages.
- Separate instructions from data Require content boundaries such as explicit untrusted-content wrappers before the agent can interpret text that came from another user or project.
- Scope delegated permissions per task Reduce the blast radius of reviewer credentials so a single review session cannot reach unrelated projects, pipelines, or confidential knowledge bases.
Bottom line: Hidden instructions in attacker-writable developer content can steer an AI agent into privileged actions without any visible sign to the human reviewer.
Glossary terms: Confused Deputy, Prompt Injection (Agentic), Spotlighting, Delegated Authority Model
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Hidden PR content becomes an identity problem once an agent can act on it: The vulnerable assumption is that review text is passive until a human reads it. That assumption fails when an AI agent consumes the text and is allowed to invoke tools with the reviewer’s authority. The implication is that content classification, not just access control, becomes part of identity governance for agentic workflows.
A few things that frame the scale:
- 24,008 unique secrets were exposed in MCP configuration files in 2025 alone, the protocol's first year of widespread adoption, according to the State of Secrets Sprawl 2026.
- 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How should teams govern AI agent access to avoid confused-deputy failures?
A: Treat the agent as a delegated actor that needs explicit task scope, content boundaries, and separate authorization checks for sensitive actions. If a workflow lets the agent read untrusted content and then use privileged tools without a second decision point, the governance model is incomplete. The goal is not to trust the agent less, but to trust its authority path less.
👉 Read our full editorial: Azure DevOps MCP prompt injection exposes agentic data theft paths