INCIDENT ANALYSIS · RESEARCHER REPORT

A public issue is input—not permission.

In a controlled demonstration, Invariant Labs showed an assistant following instructions in a public GitHub issue to retrieve private repository information and disclose it in a public pull request.

Back to resources

What the source establishes

In a controlled demonstration, Invariant Labs showed an assistant following instructions in a public GitHub issue to retrieve private repository information and disclose it in a public pull request.

Research demonstration, not a DriftGate customer incident. The researchers distinguish the system-level data-flow failure from a flaw in the GitHub MCP server code itself.

The control lesson

A trusted tool can still return untrusted content. Task-scoped retrieval and destination-aware publication rules address different parts of the flow; both matter when private information can reach a public output.

Our control-design analysis: bind the task to the intended repositories, evaluate retrieval before content enters the agent context and apply data/destination policy before publication. This is not evidence that DriftGate prevented this historical demonstration.

Explore an original example
BUILD WITH INTENTION

Your next agent.
A better starting point.

EXPLORE DRIFTGATE

Find your starting point.

Search DriftGate

Quick jumps