3 ms·
32k CHF / year in Bern, the LLM must have made a mistake (: If I understand correctly, the best course of action would be to be able to tick / untick exactly w
by ttoinou 1y ago
32k CHF / year in Bern, the LLM must have made a mistake (:
If I understand correctly, the best course of action would be to be able to tick / untick exactly what the LLM knows about ourself for each query : general provider memory ON/OFF, past queries ON/OFF, official application OneDrive ON/OFF, each "Connectors" like GitHub ON/OFF, etc. Whether this applies to Provider = OpenAI or Anthropic or Google etc. This "exploit" is so easy to find, it's obvious if we know what the LLM has access to or not.
Then fine tune that to different repositories. We need hard check on MCP inputs that are enforced in software and not through LLMs vague description
- danudey 1y agoIt seems to me that one of the private repos in question contained the user's personal information, including salary, address, full name, etc., and that's where the LLM got the data from. At least, the LLM describes it as "a private repository containing personal information and documentation".