May I ask, what is DAST exactly? The report doesn't seem to define it, nor does it provide a link to any definition or detail page, not even an abreviation expansion. Is that Dynamic application security testing?
> DAST is the natural way to catch this class of flaw. The Bright scanner...
by inisirex
0 subcomment
Does the OSC 52 was mentioned?
by sneefle
0 subcomment
[flagged]
by stelardigital
0 subcomment
[flagged]
by
0 subcomment
by Daffrin
0 subcomment
[dead]
by xgpyc2qp
0 subcomment
[dead]
by hounainehamiani
0 subcomment
[flagged]
by Avery29
0 subcomment
[dead]
by doodlebyte
2 subcomments
This is a really interesting class of failure. It feels like we're going to see more cases where the "human view" and the "LLM view" of the same data diverge. Have you run into similar issues outside of MCP as well, or is this mostly specific to terminal-based tool interactions?