3 ms·
They still don't have any scoping for the connectors. There's ZERO way our legal team will let us connect ChatGPT to Google Drive for example. ALL of our GDriv
by theshrike79 1y ago
They still don't have any scoping for the connectors.
There's ZERO way our legal team will let us connect ChatGPT to Google Drive for example. ALL of our GDrive.
Specific directories, sure. But there's no way to do it.
- red-iron-pine 1y agomirror those directories to a different namespace or location let GPT drink it up obliterate the new namespace until you need to train it again; wash, rinse, repeat
- theshrike79 1y agoNow do this for 300+ employees constantly. It's not sustainable. We need scoped MCPs before any of this is viable. The receiving end needs a setting that "user X's ChatGPT MCP can access directories [x,y,z] in Google Drive. This wouldn't require any changes to the MCP protocol in general. OR the whole spec must be changed so that when an MCP is connecting, there is a negotiation about the scope (select which directories are shared) AND that list is checked on the receiving end against a whitelist of allowed directories.