Unverified50% confidenceOpinionExact time
A read tool plus a write tool plus a loop constitutes a data exfiltration path unless some mechanism interrupts it at the tool boundary.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe read-then-write combination, in which an external write is triggered immediately after reading private data, is the classic path for data exfiltration and should be governed as an independent policy trigger condition.73% similarUnverifiedWhen a tool simultaneously possesses the two capabilities of reading user code and rendering untrusted content, it effectively becomes a potential data exfiltration springboard.73% similarUnverifiedThe fundamental logic of defending against indirect injection is the separation of data and instructions: retrieved content should be confined to a read-only data zone, and hierarchical isolation can be established by placing external content in the tool role rather than the user role.68% similarUnverifiedA parallel dirty read refers to a dependent task B reading the output of task A before it is complete, resulting in incomplete data being read; parallelism should only be applied to mutually independent nodes67% similarUnverifiedRead tools can run freely; write tools involving money, data, or external changes should go through an approval step or at least require a confirmation field.67% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1068604API
curl https://kongchang.com/api/v1/knowledge/claims/1068604MCP
get_claim(id=1068604)