execute-gitlab-issue

MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).

• Third-party content exposure detected (high risk: 0.85). Yes: in Phase 2 step 1/2 the workflow reads the full GitLab issue payload via MCP (title/description/comments/attachments) and passes that issue text into the code-autonomous engine, where the issue content is outsider-authored (i.e., not authored by the operating user).