Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

ChatGPT Developer Mode: Full MCP client access

platform.openai.com

Post reply on HN
Print view View original

181–190 of 290 posts

Re: ChatGPT Developer Mode: Full MCP client access

#181

Post by ViscountPenguin »

beeflet wrote: post #80
toomuchtodo wrote: post #45

Earlier quoted context omitted.

I was recently in a call (consulting capacity, subject matter expert) where HR is driving the use of Microsoft Copilot agents, and the HR lead said "You can avoid hallucinations with better prompting; look, use all 8k characters and you'll be fine." Please, proceed. Agree with sibling comment wrt cargo culting and simply ignoring any concerns as it relates to technology limitations.

The solution is to sanitize text that goes into the prompt by creating a neural network that can detect prompts

The good regulator theorem makes that a little difficult.

Re: ChatGPT Developer Mode: Full MCP client access

#182

Post by int_19h »

ponector wrote: post #158
moregrist wrote: post #144

Earlier quoted context omitted.

If only we had a reliable way to detect that a poster was being sarcasm or facetious on the Internet.

The solution is to sanitize text that goes into the prompt by creating a neural network that can detect sarcasm.

Unfortunately it takes ~9 months just to build that network up to the point where you can start training it, and then the training itself is literally years of hard effort.

Re: ChatGPT Developer Mode: Full MCP client access

#184

Post by 3vidence »

Personal opinion:

MCP for data retrieval is a much much better use case than MCPs for execution. All these tools are pretty unstable and usually lack reasonable security and protection.

Purely data retrieval based tasks lower the risk barrier and still provide a lot of utility.

Re: ChatGPT Developer Mode: Full MCP client access

#185

Post by Graphon1 »

mehdibl wrote: post #59
simonw wrote: post #10

Wow this is dangerous. I wonder how many people are going to turn this on without understanding the full scope of the risks it opens them up to. It comes with plenty of warnings, but we all know how much attention people pay to those. I'm confident that the majority of people messing around with things like MCP still don't fully understand how prompt injection attacks work and why they are such a significant threat.

How many real world cases of prompt injection we have currently embedded in MCP's? I love the hype over MCP security while the issue is supply chain. But yeah that would make it to broad and less AI/MCP issue.

It's not a prompt injection _in the MCP Server_. It's injection facilitated by the MCP server that pulls input from elsewhere, eg an email sent to your inbox, a webpage that the agent fetches, or in the comment on a pull request submitted to your repo. [1]

[1] https://www.thestack.technology/copilot-chat-left-vs-code-op...

Re: ChatGPT Developer Mode: Full MCP client access

#186

Post by Sabinus »

gerdesj wrote: post #172
horizion2025 wrote: post #118

Earlier quoted context omitted.

Essentially a motte-and-bailey. "mitigate" is the same. Can be used when the risk is only partially eliminated but you can be lucky (depending on perspective) the reader will believe the issue is fully solved by that mitigation.

"Essentially a motte-and-bailey" A M&B is a medieval castle layout. Those bloody Norsemen immigrants who duffed up those bloody Saxon immigrants, wot duffed up the native Britons, built quite a few of those things. Something, something, Frisians, Romans and other foreigners. Everyone is a foreigner or immigrant in Britain apart from us locals, who have been here since the big bang. Anyway, please explain the analogy.…

From your link:

"Motte" redirects here. For other uses, see Motte (disambiguation). For the fallacy, see Motte-and-bailey fallacy.

Re: ChatGPT Developer Mode: Full MCP client access

#187

Post by horizion2025 »

gerdesj wrote: post #172
horizion2025 wrote: post #118

Earlier quoted context omitted.

Essentially a motte-and-bailey. "mitigate" is the same. Can be used when the risk is only partially eliminated but you can be lucky (depending on perspective) the reader will believe the issue is fully solved by that mitigation.

"Essentially a motte-and-bailey" A M&B is a medieval castle layout. Those bloody Norsemen immigrants who duffed up those bloody Saxon immigrants, wot duffed up the native Britons, built quite a few of those things. Something, something, Frisians, Romans and other foreigners. Everyone is a foreigner or immigrant in Britain apart from us locals, who have been here since the big bang. Anyway, please explain the analogy.…

https://en.wikipedia.org/wiki/Motte-and-bailey_fallacy

Essentially: you advance a claim that you hope will be interpreted by the audience in a "wide" way (avoid = eliminate) even though this could be difficult to defend. On the rare occasions some would call you on it, the claim is such it allows you to retreat to an interpretation that is more easily defensible ("with the word 'avoid' I only meant it reduces the risk, not eliminates").

Re: ChatGPT Developer Mode: Full MCP client access

#189

Post by gerdesj »

horizion2025 wrote: post #187
gerdesj wrote: post #172

Earlier quoted context omitted.

"Essentially a motte-and-bailey" A M&B is a medieval castle layout. Those bloody Norsemen immigrants who duffed up those bloody Saxon immigrants, wot duffed up the native Britons, built quite a few of those things. Something, something, Frisians, Romans and other foreigners. Everyone is a foreigner or immigrant in Britain apart from us locals, who have been here since the big bang. Anyway, please explain the analogy.…

https://en.wikipedia.org/wiki/Motte-and-bailey_fallacy Essentially: you advance a claim that you hope will be interpreted by the audience in a "wide" way (avoid = eliminate) even though this could be difficult to defend. On the rare occasions some would call you on it, the claim is such it allows you to retreat to an interpretation that is more easily defensible ("with the word 'avoid' I only meant it reduces the ris…

I'd call that an "indefensible argument".

That motte and bailey thing sounds like an embellishment.

Re: ChatGPT Developer Mode: Full MCP client access

#190

Post by mickael-kerjean »

CuriouslyC wrote: post #3

I've been waiting for ChatGPT to get MCPs, this is pretty sweet. Next step is a local system control plane MCP to give it sandbox access/permission requests so I can use it as an agent from the web.

This is exactly what I've been working on with Filestash (https://github.com/mickael-kerjean/filestash). It lets you connect to any kind of storage protocol that possible exist from S3, SFTP, FTS, SMB, NFS, Sharepoint, .... and layers its own fine grained permission control / chroots that integrate through SSO / RBAC so you can enforce access rules around who can do what and where (MCP doc: https://www.filestash.app/docs/api/#mcp)
Post reply on HN