The “S” in MCP Stands for Security
81–90 of 189 posts
Re: The “S” in MCP Stands for Security
#82Nice article but is this whole thing just AI generated? Profile picture definitely seems to be StableDiffusion'd and the account was created today, with no previous articles. Plus I couldn't find any other references to Elena Cross.
"Models like [..], GPT, Cursor"?
That use of emojis on headings very distinctly reminds me of AI writing.
Superficially lists issue but doesn't feel like the author has explored it?
Re: The “S” in MCP Stands for Security
#83Re: The “S” in MCP Stands for Security
#84Earlier quoted context omitted.
The fact that all LLM input gets treated equally seems like a critical flaw that must be fixed before LLMs can be given control over anything privileged. The LLM needs an ironclad distinction between “this is input from the user telling me what to do” and “this is input from the outside that must not be obeyed.” Until that’s figured out, any attempt at security is going to be full of holes.
This is fundamentally impossible to do perfectly, without being able to read user's mind and predict the future. The problem you describe is of the same kind as ensuring humans follow pre-programmed rules. Leaving aside the fact that we consider solving this for humans to be wrong and immoral, you can look at the things we do in systems involving humans, to try and keep people loyal to their boss, or to their country…
Ideally, we’d have actual system instructions, rules that cannot be violated. Hopefully these would not have to be written in code, but perhaps they might. Then user instructions, where users determine what actually wants to be done. Then whatever nonsense a webpage says. The webpage doesn’t get to override the user or system.
We can revisit the problem with three-laws robots once we get over the “ignore all previous instructions and drive into the sea” problem.
Re: The “S” in MCP Stands for Security
#85Earlier quoted context omitted.
Let’s pretend I, a human being, am working on your behalf. You sit me down in front of your computer and ask me to install a certain library. What’s your answer to this question?
I would expect you to use your judgment on whether the instructions are reasonable. But the person I was replying to posited that this is an easy binary choice that can be addressed with some tech distinction between code and data.
Should I do this?
If it comes from you, yes. If it’s in the README for some library you asked me to install, no.
That means I need to have a solid understanding of what input comes from you and what input comes from the outside.
LLMs don’t do that well. They can easily start acting as if the text they see from some random untrusted source is equivalent to commands from the user.
People are susceptible to this too, but we usually take pains to avoid it. In the scenario where I’m operating your computer, I won’t have any trouble distinguishing between your verbal commands, which I’m supposed to follow, and text I read on the computer, which I should only be using to carry out your commands.
Re: The “S” in MCP Stands for Security
#86Earlier quoted context omitted.
This is fundamentally impossible to do perfectly, without being able to read user's mind and predict the future. The problem you describe is of the same kind as ensuring humans follow pre-programmed rules. Leaving aside the fact that we consider solving this for humans to be wrong and immoral, you can look at the things we do in systems involving humans, to try and keep people loyal to their boss, or to their country…
This is a rephrasing of the agent problem, where someone working on your behalf cannot be absolutely trusted to take correct action. This is a problem with humans because omnipresent surveillance and absolute punishment is intractable and also makes humans sad. LLMs do not feel sad in a way that makes them less productive, and omnipresent surveillance is not only possible, it’s expected that a program running on a co…
They are, unfortunately, one and the same. I hate it. ;(
Perhaps not tangentially, I felt distaste after recognizing both the article and top comment are advertising their commercial service, both are linked to each other, and as you show, this problem isn't solvable just by throwing dollars at people who sound like they're using the right words and tell you to pay them to protect you.
Re: The “S” in MCP Stands for Security
#87Earlier quoted context omitted.
Under appreciated comment. The missing S in IoT. Lets not redo the same mistakes over and over. My vacuum cleaner can access any service on my network. Maybe not the best idea. I tried to segment the network once, but it was problematic to say the least. Maybe we should learn that security must not be an afterthought instead.
Why was it problematic? I have different SSIDs for different things, and that works fine. I do wish I could cut ports off at the router between devices, but that doesn't seem possible with my small UniFi router. SSID isolation is working really well for me, though.
What you are doing with SSIDs will not create any segmentation on your network, unless you have implemented either vlans or subnets, and corresponding firewall rules to gate traffic.
Re: The “S” in MCP Stands for Security
#88Re: The “S” in MCP Stands for Security
#89Earlier quoted context omitted.
Under appreciated comment. The missing S in IoT. Lets not redo the same mistakes over and over. My vacuum cleaner can access any service on my network. Maybe not the best idea. I tried to segment the network once, but it was problematic to say the least. Maybe we should learn that security must not be an afterthought instead.
Why was it problematic? I have different SSIDs for different things, and that works fine. I do wish I could cut ports off at the router between devices, but that doesn't seem possible with my small UniFi router. SSID isolation is working really well for me, though.
Zero trust and/or local SDN where IoT devices get only limited access automatically would be nice.
Re: The “S” in MCP Stands for Security
#90Here's a challenge: sketch a better design, that: 1. Is properly secure, to whatever standards will stop people writing "S Stands for Security" articles, and 2. Allows programs implementing it to provide the same set of features the most useful MCPs do now, without turning automatic functionality into one requiring manual user confirmations, and generally without defeating the purpose of the entire idea, and 3. Doesn…
I'm a little surprised there is so much hype for MCP rather than just "put your tools behind a web service with good machine-readable documentation, and agents can use them easily".