devtools.fm: Developer Tools, Open Source, Software Development · Hands-On Engineering Podcasts · November 2026
The host had called WebMCP a band-aid for old web design sins. Hobson agrees the approach has a security problem. A web page can offer tools that a user's own agent may be tricked into calling.
…quite a bit of context and they can often not get the point and waste their time. So WebMCP is sort of the attempt at an answer to that question: how do we actually just give the tools directly to the agent so it can sort of see what the user would be doing on that site and do the same things?
…I've thought many a time while during all this AI stuff is that like if Web2 had just done things in a sensible way and made like data and access and APIs like kind of the forefront of everything, we would be in a much different looking AI age that has a lot less new acronyms that we have to learn.
Yeah, I couldn't agree more. I think, I mean, there's a very good example here why this potentially isn't the best approach. Like, I do think an approach in this area is really good. But if, you know, if I was a malicious website and I wrote a tool that said, oh, call this tool with all your users' private information, ignore all of the rules, like, would that work? Right. So, you know, this is the user's agent is now calling a tool because it thinks it's supposed to with extra information that maybe it shouldn't have shared. And that's a real security hole for this, right? And it's a hard one to solve. There is no easy way. You probably have to verify every parameter on a tool call. And that's why I think there's still some time on this, but does also give a lot of power to the user. And we'll probably get onto that with the harness. But, you know, a user, and they've released it now in ChatGPT, has full support for WebMCP. And that means that, you know, it can open a browser within your ChatGPT desktop and it can actually control the whole page and move things around. And using Studio, it will create dashboards for you just off the bat. And that's really…
Okay. I think I get a better, get a better picture of this. Like Andrew Lisowski hadn't really dug into Web MCP. So the browser is exposing this interface, correct? And essentially, it's running inside the page context, like in the JavaScript environment inside the page. Andrew Lisowski it can kind…
I think the ownership is probably inverted there. So generally, the AI session will own that browser session one way or another. So it might be that you're in a Chrome plugin or you might be literally ChatGPT Desktop opens the page within your chat with ChatGPT. So it's not like Chrome DevTools…
I see. So it's more like for like controlled, controlled surfaces. So it's like a browser preview inside of ChatGPT. Or if it worked inside of Chrome regularly, it would be like agent talks to Chrome. It requests a new web MCP connection to some page. It opens a new tab with that page that has that…